Skip to main content
Glama

FinanceQuery

Earnings Call Transcripts

get_transcripts
Read-onlyIdempotent

Get earnings call transcripts for a company. Returns paragraph-by-paragraph text (speaker, timestamp, text), paginated via paragraph_limit/paragraph_cursor since a full call can be tens of thousands of tokens.

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>"
    },
    "name": "get_transcripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoTarget language for translated text fields (BCP 47, e.g. "ja", "zh-Hant"); English or omitted = no translation
limitNoMaximum number of transcripts to return (default: all)
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
symbolYesStock ticker symbol
paragraph_limitNoMaximum transcript paragraphs per page; omitted = curated default (25). A full call's `text` is returned as paginated paragraphs, not one giant blob
paragraph_cursorNoOpaque continuation token from a previous response's paragraphs `pageInfo.endCursor`; omitted = first page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the return shape (speaker, timestamp, text) and the important scale warning that a full call can be tens of thousands of tokens, which motivates pagination. It does not cover ordering, availability coverage, or what happens at the end of pagination.

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, zero waste, with the resource and return shape front-loaded and the scaling caveat immediately after. Nothing is padded or restated from the title.

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 6-param read-only tool with no output schema, the description covers what the tool returns and why pagination matters, which is the key completeness risk here. The remaining gap is disambiguation from the near-identically named sibling, which matters given how easily an agent could pick the wrong one.

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 coverage is 100%, so all six parameters are already documented in the schema, including the paragraph_limit default of 25 and the pageInfo.endCursor origin for paragraph_cursor. The description repeats the pagination rationale rather than adding syntax or edge-case meaning, 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?

States a clear verb+resource: 'Get earnings call transcripts for a company.' The plural resource and 'paragraph-by-paragraph text' differentiate it somewhat, but the description never distinguishes it from the singular sibling get_earnings_transcript, leaving a real ambiguity for an agent choosing between the two.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, and no mention of alternatives such as get_earnings_transcript. The only operational hint is that pagination exists, which is usage mechanics rather than tool selection 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.