Skip to main content
Glama

Get full call transcript

get_call_transcript
Read-only

Full turn-by-turn transcript for a call you own. Use this after lifecycle is finalized to decide if the user's goal succeeded. Do not treat outcome answered as success.

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": {
      "call_id": "<call_id>"
    },
    "name": "get_call_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
call_idYesCall id to read the full transcript for.

Output Schema

NameRequiredDescriptionDefault
transcriptYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds the ownership scoping constraint ("a call you own") and a substantive interpretation warning about the answered outcome. It does not mention how long transcripts behave or any size/pagination limits, which is the main remaining behavioral gap.

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?

Three short sentences with zero padding: purpose first, then the timing precondition, then the outcome caveat. Every sentence contributes a distinct decision-relevant fact.

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?

A simple one-parameter read tool with an output schema that can carry return structure, and the description covers purpose, timing, ownership, and interpretation pitfalls. Only minor gaps remain, such as whether the call fails when lifecycle is not finalized.

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?

With a single parameter at 100% schema coverage, the schema fully documents call_id, so the baseline of 3 applies. The description adds only the implicit constraint that the call must be one you own, without any format or validity detail beyond the schema's minLength requirement.

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?

"Full turn-by-turn transcript for a call you own" gives a specific verb (read transcript) and resource (call), and the phrase "full turn-by-turn" differentiates it from metadata-oriented siblings like get_call. It stops short of explicitly naming the sibling to use for non-transcript call data, so differentiation is implied rather than stated.

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 states a clear usage condition: call this "after lifecycle is finalized" when you need to judge whether the user's goal succeeded. It also gives negative guidance — do not equate an "answered" outcome with success. It does not name an alternative tool for pre-finalization or metadata lookups, so there is no explicit routing to a sibling.

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.