Skip to main content
Glama
Sign In

ticker-scout

by ai.tickerscout
OverviewDiscussionsAdmin

Financial statements (the whole record)

get_financials
Read-onlyIdempotent

Income statement, balance sheet and cash flow, already assembled from a company's SEC filings, for up to three fiscal years plus the latest quarter, year to date and trailing twelve months, with segment tables, per-share figures and the record's own notes. This is the published financials.json, whole or by top-level section. Already assembled: no XBRL concept selection, no deriving a discrete quarter from year-to-date columns, no scale factor to infer. Section names differ per company, so call with no sections first (or read available_sections) and then request only what you need. Request the figure_sources section by name for a sec.gov link to the line of the filing that prints each figure; a whole-file call leaves it out. All money is in actual dollars (not thousands, not millions), per-share figures in dollars per share (per ADS for a foreign issuer that has one), share counts in actual shares, split-adjusted. A foreign issuer's figures are converted to US dollars at the rate recorded on each period. For one statement or one period, searching older records too, use get_statements; for one figure, get_figure.

Input Schema

NameRequiredDescriptionDefault
recordNoAn earlier published record, by tag ('FY27Q1') or by the period its filing reports ('Q1 FY2027'). Omit for the latest. list_periods lists every record.
tickerYesTicker symbol, case-insensitive. Examples: NVDA, brk-b, BRK.B.
sectionsNoTop-level sections to return, for example annual, quarterly, trailing_twelve_months, notes, uncertainties, figure_sources. Omit for the whole file (without figure_sources). An unknown name returns the valid list for that company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sections / description
      Previous value: -"Top-level sections to return, for example annual, quarterly, trailing_twelve_months, notes, uncertainties, figure_sources. Omit for the whole file, which leaves out figure_sources. An unknown name returns the valid list for that company."New value: +"Top-level sections to return, for example annual, quarterly, trailing_twelve_months, notes, uncertainties, figure_sources. Omit for the whole file (without figure_sources). An unknown name returns the valid list for that company."
  2. Changed2 schema fields changed
    • addedInput schema / properties / record
      Added value: +{
+  "description": "An earlier published record, by tag ('FY27Q1') or by the period its filing reports ('Q1 FY2027'). Omit for the latest. list_periods lists every record.",
+  "type": "string"
+}
    • changedInput schema / properties / ticker / description
      Previous value: -"Ticker symbol, case-insensitive. Examples: NVDA, brk-b."New value: +"Ticker symbol, case-insensitive. Examples: NVDA, brk-b, BRK.B."
  3. Changed1 schema field changed
    • changedInput schema / properties / sections / description
      Previous value: -"Top-level sections to return, for example annual, quarterly, trailing_twelve_months, notes, uncertainties. Omit for the whole file. An unknown name returns the valid list for that company."New value: +"Top-level sections to return, for example annual, quarterly, trailing_twelve_months, notes, uncertainties, figure_sources. Omit for the whole file, which leaves out figure_sources. An unknown name returns the valid list for that company."
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations cover the safety profile (readOnly, idempotent, non-open-world), and the description goes well beyond them: a whole-file call silently omits figure_sources, figure_sources yields a sec.gov link to the printing line, an unknown section name returns the valid list, section names vary per company, and all units/conversion rules are spelled out. These are non-obvious behaviors an agent could not infer from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded with what the tool returns, followed by usage rules and then units/conversion caveats, so the ordering is sound. It is dense and long — the units and foreign-issuer conversion material is useful but could be tightened — yet no sentence is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must convey the return shape, and it does: statements, segment tables, per-share figures, notes, YTD/TTM columns, and the units of every figure. Combined with the section-selection guidance, an agent has everything needed to call and interpret this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic value: it explains that section names differ per company, that omitting sections returns everything except figure_sources, and that requesting figure_sources by name returns source links. The record parameter's meaning is only hinted at via list_periods rather than explained in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb-phrase identifying the resource ('Income statement, balance sheet and cash flow, already assembled from a company's SEC filings') and states the coverage window precisely. It explicitly distinguishes itself from get_statements ('for one statement or one period') and get_figure ('for one figure'), so an agent can route correctly without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit call procedure ('call with no sections first (or read available_sections) and then request only what you need') and names both alternatives with the condition that selects each: get_statements for one statement/one period, get_figure for a single figure. Both when-to-use and when-not-to-use are present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ticker-scout toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources