Skip to content

Agent Guide

Use this page when an agent needs to decide which command to call. Use tools.json for exact parameter schemas, output schemas, side-effect labels, and command-specific routing notes.

  1. llms.txt for the compact entry point.
  2. AI Integration & Skills when installing the local skill.
  3. tools.json for command schemas and side effects.
  4. Agent Output Formats when compact record output is enough.
  5. The relevant namespace page for examples and result shape.
  6. trust before summarizing evidence.

Agents that support skills can install finance-cli-skills.zip. The skill tells agents to call the installed finance executable with JSON output, read tools.json for schemas, and preserve source-aware citations.

Use --output json for canonical audit output. Use --output compact or --output schema when a task only needs normalized facts in a smaller LLM context.

User asks forPreferWhy
Latest filings or a filing URL/accessionfilings.recentFinds SEC filing candidates and preserves accession/source metadata.
XBRL financial statement rowsfilings.statementReturns structured income, balance, or cashflow rows.
A known SEC report tablefilings.reports, then filings.reportDiscovers report names before reading rows.
Narrative 10-K sectionsfilings.sections, then filings.readUses canonical section keys such as business, risk factors, MD&A, and segments.
Phrase or table discovery inside a filing/documentdocument.scanReturns match IDs and character offsets for follow-up reads.
More context around a scan hitdocument.windowReads a bounded window by offset or match ID.
Scanned/image-heavy PDFsdocument.ocrOCR fallback after native text extraction is not enough.
Explicit finance mathformula.*Deterministic calculators with inputs and method.
DCF, NPV, IRR, WACC, scenario mathvaluation.*Deterministic valuation helpers from explicit assumptions.
Current quote, bars, market status, broad contextmarket.*Provider-attributed market data and summaries.
Sector, industry, or Yahoo screen discoverysector.*, industry.*, screen.*Discovers supported keys and runs predefined market views.
Earnings calendar fieldscalendar.*Company calendar and earnings-date rows.
News/event contextnews.*, price.contextSource-attributed event windows and dated context.
Transcripts and KPI evidencetranscripts.*, kpi.*Preserves transcript URLs, quarters, snippets, and metric labels.
Reproducible strategy checkbacktest.*Uses explicit symbols, dates, strategy names, and parameters.
Provider setup/debuggingsources.*Lists capabilities and probes configured providers.
  • Use formula.* only when all numeric inputs are explicit in the user prompt or extracted from cited command output.
  • Use valuation.* only for deterministic math. Do not describe valuation output as investment advice.
  • If an input is missing, ask for it or run the appropriate extraction command first.
  • Cite accession, url, report_name, section, page, start_char, end_char, match_id, source, provider, and timestamp when available.
  • Treat Yahoo, FMP, SEC, GDELT, transcripts, and company IR as source-specific records, not ground truth.
  • Never present market data without source/provider and date/timestamp fields when available.
  • Preserve warnings; they are part of the result.
  • If ok=false, surface error directly and do not fabricate replacement data.
  • If ok=true with empty arrays, report that no matching records were returned by that source.
  • If ok=true with warnings, summarize the usable data and keep the warnings attached.
  • If a command needs a provider key or dependency, let the command fail clearly and show the error.