Skip to main content
Glama

FinanceQuery

Earnings Call Transcript

get_earnings_transcript
Read-onlyIdempotent

Get an earnings call transcript for a symbol. Provide quarter and year for a specific call, or omit both for the latest (Yahoo only).

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": {
      "symbol": "<symbol>",
      "quarter": "<quarter>"
    },
    "name": "get_earnings_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoFiscal year. See `quarter`
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
symbolYesStock ticker symbol
quarterYesFiscal quarter (Q1, Q2, Q3, Q4). Required alongside `year` for providers with no "latest" shortcut (Alpha Vantage); Yahoo defaults to latest when omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one genuinely new behavioral trait: the 'latest' shortcut is provider-dependent ('Yahoo only'). However, it does not say what happens on providers without that shortcut, does not describe the returned structure (speaker segments, dates), and its 'omit both' instruction conflicts with the schema listing quarter as required, leaving the agent unsure of the true contract.

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

Conciseness5/5

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

Two sentences with zero filler, and the primary action comes first with the calling convention second. Every clause earns its place, including the parenthetical provider caveat.

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?

For a read-only four-parameter fetch with no output schema, the definition covers the essential calling convention and the provider caveat. An agent could invoke it correctly, though it would benefit from a note on return shape and on whether omitting quarter is actually accepted given the schema marks it required.

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 both symbol and quarter (including the Alpha Vantage 'no latest shortcut' caveat and Yahoo default) are already documented in the schema. The description's parameter content largely restates that rather than adding new meaning, so the baseline 3 applies. It adds nothing about the year/fields parameters.

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 gives a specific verb and resource ('Get an earnings call transcript') plus the scoping entity ('for a symbol'), which is enough to tell it apart from adjacent tools like get_earnings_surprises or get_financials by resource alone. It stops short of naming an alternative explicitly, so it is clear rather than exemplary.

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 gives a concrete call recipe: supply quarter and year for a specific call, or omit both to get the latest. It also carries a useful exclusion in '(Yahoo only)' for the latest shortcut. What is missing is any guidance on when to prefer this tool over other earnings-related siblings, but the conditional usage instruction is clear.

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.