Skip to main content
Each tool wraps one REST route and returns its envelope unchanged. The endpoint page for each route documents the full parameters and response; the columns below are the map.
ToolREST routePlanDocs
stockcontext_searchGET /v2/searchFreesearch
stockcontext_coverageGET /v2/coverageFreecoverage
stockcontext_snapshotGET /v2/snapshotFreesnapshot
stockcontext_valuationGET /v2/valuationFreevaluation
stockcontext_priced_inGET /v2/priced-inPaidpriced-in
stockcontext_compareGET /v2/comparePaidcompare
stockcontext_profileGET /v2/profilePaidprofile
stockcontext_fundamentalsGET /v2/fundamentalsPaidfundamentals
stockcontext_earningsGET /v2/earningsPaidearnings
stockcontext_dividendsGET /v2/dividendsPaiddividends
stockcontext_technicalsGET /v2/technicalsPaidtechnicals
stockcontext_price_actionGET /v2/price-actionPaidprice-action
stockcontext_historyGET /v2/historyPaidhistory
stockcontext_calendarGET /v2/calendarPaidcalendar
stockcontext_filings_listGET /v2/filingsPaidfilings list
stockcontext_filings_getGET /v2/filings/{accession}Paidfiling
stockcontext_filings_sectionGET /v2/filings/{accession}/section/{name}Paidfiling section
stockcontext_insiderGET /v2/insiderPaidinsider
stockcontext_eventsGET /v2/eventsPaidevents
stockcontext_factsGET /v2/factsPaidfacts
stockcontext_filing_diffGET /v2/filings/{accession}/diffPaidfiling diff
Free tools are search, coverage, snapshot, and valuation. Every Paid tool needs a paid plan — Starter or Builder both satisfy it. For per-plan rate limits and quotas, see plans and limits. Segments, ownership/13F/13D-G, and governance are private beta: their REST routes remain available only for explicitly enabled integrations, but they are not part of the default public MCP tool surface.

Argument conventions

Tool arguments are native JSON, not query strings. Three rules cover everything:
  • Lists are arrays. symbols for compare is ["AAPL", "NVDA"]; forms for filings is ["10-K", "10-Q"]; series for history is a list. Do not pass comma-separated strings. The arrays have bounds: compare takes 2–12 unique symbols and up to 24 fields, filings takes up to 4 forms, and history takes up to 3 series on a single cadence.
  • The history window argument is named period. It maps to the REST range parameter (whose own legacy alias is also period), so values like 1y, 5y, ytd, and max apply. History also takes cadence (daily, weekly, quarterly, annual, per-payment), and series: ["dividend"] requires cadence: "per-payment" explicitly.
  • Everything else mirrors the REST query params with the same names and bounds: REST symbols match ^[A-Z0-9-]{1,8}$ after normalization, while the tool schemas are more permissive (^[A-Za-z0-9.-]{1,8}$) and lowercase or dot forms like brk.b normalize server-side. limit is 1–100 for filings and 1–200 for insider, section name is one of business, risk_factors, mda, quantitative_qualitative_disclosures, controls_and_procedures, press_release.
The linked endpoint page is the full reference for each tool’s parameters and response fields.