Finbolt

earnings_release

The quarterly earnings release from the company's 8-K, as the company printed it: headline figures (GAAP, non-GAAP and operating measures) with period and scale, the company's guidance word for word, and beside each figure the SEC-tagged figure for the same quarter and for the quarter before. matches_tagged says whether the printed and tagged figures agree. Differences are shown, never reconciled, and nothing is merged into get_fact. A quarter just released has no tagged figure until its 10-Q or 10-K is filed. Set all_cells to true to get every figure in the release that matches one of our line items. 1 credit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "earnings_release"
  }
}

Input Schema

Name	Required	Description	Default
`period`	No	'latest', a fiscal quarter 'FY2026 Q3', the quarter's end date '2026-09-30', or the 8-K's accession number	latest
`company`	Yes	Ticker (e.g. 'AAPL') or SEC CIK
`all_cells`	No	Leave false to get the headline figures and the guidance. Set true to get every figure in the release that matches one of our line items, which can be long.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.1/5.0

Behavior5/5

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

With no annotations present, the description carries the full burden and does so well: it discloses the reconciliation policy ('Differences are shown, never reconciled'), the staleness rule for new quarters, the size risk of all_cells ('can be long'), and the cost ('1 credit'). It also notes the data is not merged into get_fact, which prevents a downstream misuse.

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?

It is front-loaded with what the tool returns and every clause carries information (scale, period, matches_tagged, no reconciliation, filing lag, cost). The all_cells sentence largely duplicates the schema's own wording and could be trimmed, but nothing else is filler.

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

Completeness4/5

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

An output schema exists, so the description need not explain the response shape, and it still flags the two things an agent must know before calling: the filing-lag gap and the cost. It does not say what happens if period matches nothing or how 'latest' resolves when no release exists, which leaves a small operational gap.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters are already documented in the schema, including the period formats and the all_cells tradeoff. The description restates the all_cells semantics and the headline-vs-full default but adds no new syntax or format detail beyond the schema, so baseline 3 applies.

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

Purpose4/5

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

The description states a specific resource and its distinguishing shape: the 8-K release 'as the company printed it', headline GAAP/non-GAAP/operating figures plus verbatim guidance, each paired with the SEC-tagged figure and a matches_tagged flag. It explicitly contrasts with get_fact ('nothing is merged into get_fact'), but does not differentiate from the similar-sounding sibling fetch_earnings or from financials.

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

Usage Guidelines4/5

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

It makes the use case clear (see printed vs tagged figures side by side, and whether they agree) and adds a real exclusion: a just-released quarter has no tagged figure until its 10-Q/10-K is filed, so the comparison half will be empty. It stops short of naming the sibling to use instead when a tagged-only or as-reported-only view is wanted.

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

All Finbolt tools Inspect

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

Need Help?