Skip to main content
Glama

Get call status

get_call
Read-only

Read the current state of a call you own. Lifecycle is queued → dialing → answered → finalized. Returns a short transcript tail only. When finalized, read outcome and then get_call_transcript to judge the user's goal. outcome is the phone network, not task 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
call_idYesCall id returned by place_call, place_call_and_track, or place_call_and_wait.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered structurally. The description still adds real behavioral value with "Returns a short transcript tail only" and the important semantic caveat that outcome reflects the phone network rather than task success.

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 short sentences, front-loaded with the purpose, then lifecycle, then return semantics, then the caveat. Nearly every clause earns its place; only the transition into get_call_transcript feels slightly compressed into the same sentence as the outcome caveat.

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?

For a single-parameter read-only tool with an output schema, the description covers purpose, lifecycle stages, what portion of the result matters, and how outcome differs from task success, and it points to the correct follow-up tool. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the call_id field already documents its origin (place_call, place_call_and_track, place_call_and_wait) and minimum length. Confidential: the description adds the ownership constraint ("a call you own"), which is a meaningful invocation condition beyond the raw schema.

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 and resource ("Read the current state of a call") plus the scope constraint ("a call you own") and a concrete lifecycle model (queued → dialing → answered → finalized). It also distinguishes itself from the sibling it is not, naming get_call_transcript as the next step once finalized.

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?

Gives clear when-to-use context: poll state during the call, then when finalized read outcome and move to get_call_transcript to judge the user's goal. It does not explicitly state polling cadence or when to prefer get_call over list_calls, but the sequencing guidance toward the transcript sibling is concrete and actionable.

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.