Skip to main content
Glama

Get earnings call transcript

get_earnings_call_transcript

Read cached earnings-call paragraphs for one exact Bullrun ticker, optionally filtered by fiscal period or search text. A best-effort free background import collects at most the two latest retained calls for supported US listings, with a 24-hour stored-data cooldown; the first read may be empty. Coverage and source publication lag vary. Speaker names and paragraph order are retained; roles and prepared/Q&A section labels may be unavailable. Does not change portfolios or user data.

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": "get_earnings_call_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoOptional case-insensitive text/speaker search across transcript chunks.
tickerYesBullrun ticker, e.g. "CRWD", "SPGI", "V". Use the listing ticker returned by search_stocks. US/European examples: AAPL, BMW, NESN. Most Asian listings keep their exchange suffix (6324.T, 0700.HK); some use bare codes (005930). Native or suffixed forms resolve only when one listing matches; search by company name or ISIN if unsure.
maxChunksNoMaximum speaker-tagged transcript chunks to return.
fiscalYearNoOptional fiscal year filter.
fiscalQuarterNoOptional fiscal quarter filter.
maxCharsPerChunkNoMaximum characters per transcript chunk in the MCP response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Bullrun ticker, e.g. \"CRWD\", \"SPGI\", \"V\". Bullrun tickers: US and most European listings use the plain local symbol (AAPL, BMW, NESN, ABBN); most Asian and Indian listings keep their exchange suffix (Tokyo 6324.T, Hong Kong 0700.HK, Shanghai 600519.SS, Shenzhen 000001.SZ, Taiwan 2330.TW, Korea 000100.KS, Singapore D05.SI, India RELIANCE.NS), but some Japanese and Korean large caps are plain codes (Toyota 7203, Samsung 005930). Either form is resolved automatically when exactly one listing matches; use search_stocks to find a ticker by company name or ISIN."New value: +"Bullrun ticker, e.g. \"CRWD\", \"SPGI\", \"V\". Use the listing ticker returned by search_stocks. US/European examples: AAPL, BMW, NESN. Most Asian listings keep their exchange suffix (6324.T, 0700.HK); some use bare codes (005930). Native or suffixed forms resolve only when one listing matches; search by company name or ISIN if unsure."
  2. Changed1 schema field changed
    • changedInput schema / properties / maxChunks / default
      Previous value: -80New value: +40
  3. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"The ticker exactly as listed on Bullrun, e.g. \"CRWD\", \"SPGI\", \"V\"."New value: +"Bullrun ticker, e.g. \"CRWD\", \"SPGI\", \"V\". Bullrun tickers: US and most European listings use the plain local symbol (AAPL, BMW, NESN, ABBN); most Asian and Indian listings keep their exchange suffix (Tokyo 6324.T, Hong Kong 0700.HK, Shanghai 600519.SS, Shenzhen 000001.SZ, Taiwan 2330.TW, Korea 000100.KS, Singapore D05.SI, India RELIANCE.NS), but some Japanese and Korean large caps are plain codes (Toyota 7203, Samsung 005930). Either form is resolved automatically when exactly one listing matches; use search_stocks to find a ticker by company name or ISIN."
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations mark readOnlyHint=false, and the description explains why: a free background import fetches at most two retained calls with a 24-hour stored-data cooldown, so the call has side effects and a cold-start empty result. That is genuinely non-obvious context beyond the annotations, and "does not change portfolios or user data" bounds the blast radius. Not a 5 only because the import's trigger/queue behavior (does the call block while importing?) is not spelled out.

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?

Three sentences, all substantive, with the core read action front-loaded before caveats. Slightly dense — the cooldown, coverage, and field-fidelity caveats are packed into long clauses — but none 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?

With 6 params, no output schema, and an unusual cached-import model, the description covers the necessary ground: return form (speaker-tagged chunks), retained vs. missing fields (speaker names and order kept; roles and Q&A labels may be absent), and freshness limits. It stops short of describing whether call metadata (period, date, source) accompanies the chunks, which an agent would want without an output schema.

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% and each parameter already carries a precise description (including ticker resolution rules and chunk/char caps), so the schema does the heavy lifting. The description only restates that filtering is by fiscal period or search text; it adds no syntax or interaction detail (e.g., that maxChunks/maxCharsPerChunk trade off against each other). Baseline 3 is appropriate.

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?

States a specific verb plus resource ("Read cached earnings-call paragraphs") and scope ("one exact Bullrun ticker"), plus the optional filter dimensions. No sibling tool touches transcripts, so the resource alone is differentiating against news, financials, and company-data tools.

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 implied rather than instructed: the agent learns the first read may be empty and coverage/lag vary, which tells it how to interpret a thin result, but the description never states when to prefer this over (or in addition to) get_company_news or get_financial_history for earnings context. No explicit when-not 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.