Skip to main content
Glama

AINDEX

A US company's latest earnings release

earnings_release
Read-only

A US company's latest results in its own words, from its SEC filing (8-K item 2.02): the press release with revenue, profit, guidance and management's comments, then any other exhibit filed with it, such as a CFO's commentary. Up to 12,000 characters, with links to the full documents. Not the call's questions and answers. Free, from SEC EDGAR.

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": {
      "ticker": "<ticker>"
    },
    "name": "earnings_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description earns credit for adding genuinely useful behavior: an explicit ~12,000-character truncation cap, links out to the full documents, and coverage of any co-filed exhibit. With annotations carrying the read-only signal, this is solid but not exceptional disclosure.

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 a single dense sentence, front-loaded with the resource and its source before the qualifying details, and every clause carries information (filing form, contents, extras, length cap, exclusion). The parenthetical and trailing clauses make it slightly heavy for one sentence, but there is no filler.

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?

No output schema exists, so the description carries the return-value burden and does so: it specifies what documents come back, that they are excerpts capped at 12,000 characters, and that links to full versions are included. For a one-parameter read-only lookup, nothing an agent needs in order to call it correctly is missing.

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?

There is one parameter at 0% schema description coverage, so the description must compensate, and it does only partially: "a US company's" implies the ticker is restricted to US-listed issuers, which is real meaning beyond the bare pattern-regex in the schema. It gives no ticker format, exchange, or class-share syntax guidance to pair with the `^[A-Za-z.]{1,10}$` pattern. Adequate but leaves the only parameter under-explained.

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 names the exact artifact (the 8-K item 2.02 press release) and enumerates its contents: revenue, profit, guidance, management comments, plus additional exhibits like CFO commentary. It also carves out what it is not ("Not the call's questions and answers"), which separates it from transcript-style tools. It never names the closely related sibling get_earnings, so an agent must infer the boundary rather than being told it.

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

Usage Guidelines3/5

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

Usage is only implied: "latest results" establishes recency, and the Q&A exclusion signals one alternative to avoid. There is no explicit statement of when to choose this over get_earnings or get_financials, and no prerequisites or failure conditions are given. The "Free, from SEC EDGAR" note does hint at cost/access considerations but is not framed as guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources