Skip to main content
Glama

Get a call

get_call
Read-onlyIdempotent

Get a call. One call from the history. Returns 404 for a call in a conversation you cannot open. Requires feature: whatsapp_calling for a WhatsApp call, voice_agents for an AI call, voice_integrations for an imported call.

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": {
      "id": "<id>"
    },
    "name": "get_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID of the call
fieldsNoOptional: return only these fields of each record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fields / items / enum
      Previous value: -[
      -  "id",
      -  "provider",
      -  "direction",
      -  "status",
      -  "end_reason",
      -  "duration_seconds",
      -  "created_at",
      -  "started_at",
      -  "ended_at",
      -  "from_number",
      -  "to_number",
      -  "inbox",
      -  "contact",
      -  "conversation_id",
      -  "message_id",
      -  "accepted_by_agent",
      -  "recording_url",
      -  "recording_duration_s",
      -  "ai_handled",
      -  "engine",
      -  "agent_bot",
      -  "voice_line_id",
      -  "sentiment",
      -  "call_outcome",
      -  "dial_cause",
      -  "campaign_id",
      -  "campaign_contact_id",
      -  "updated_at"
      -]New value: +[
      +  "id",
      +  "provider",
      +  "direction",
      +  "status",
      +  "end_reason",
      +  "duration_seconds",
      +  "created_at",
      +  "started_at",
      +  "ended_at",
      +  "from_number",
      +  "to_number",
      +  "inbox",
      +  "contact",
      +  "conversation_id",
      +  "message_id",
      +  "accepted_by_agent",
      +  "recording_url",
      +  "recording_duration_s",
      +  "ai_handled",
      +  "engine",
      +  "agent_bot",
      +  "voice_line_id",
      +  "parent_call_id",
      +  "ai_transfer_hop",
      +  "sentiment",
      +  "call_outcome",
      +  "dial_cause",
      +  "disposition_gap",
      +  "campaign_id",
      +  "campaign_contact_id",
      +  "campaign_interest",
      +  "updated_at"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / fields / items / enum
      Previous value: -[
      -  "id",
      -  "provider",
      -  "direction",
      -  "status",
      -  "end_reason",
      -  "duration_seconds",
      -  "created_at",
      -  "started_at",
      -  "ended_at",
      -  "from_number",
      -  "to_number",
      -  "inbox",
      -  "contact",
      -  "conversation_id",
      -  "message_id",
      -  "accepted_by_agent",
      -  "recording_url"
      -]New value: +[
      +  "id",
      +  "provider",
      +  "direction",
      +  "status",
      +  "end_reason",
      +  "duration_seconds",
      +  "created_at",
      +  "started_at",
      +  "ended_at",
      +  "from_number",
      +  "to_number",
      +  "inbox",
      +  "contact",
      +  "conversation_id",
      +  "message_id",
      +  "accepted_by_agent",
      +  "recording_url",
      +  "recording_duration_s",
      +  "ai_handled",
      +  "engine",
      +  "agent_bot",
      +  "voice_line_id",
      +  "sentiment",
      +  "call_outcome",
      +  "dial_cause",
      +  "campaign_id",
      +  "campaign_contact_id",
      +  "updated_at"
      +]
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description is not obligated to restate safety. It adds real value beyond them by disclosing the 404 case for calls in conversations the caller cannot open and the feature flags required per call type (whatsapp_calling, voice_agents, voice_integrations). It omits any note on response shape or rate limits, which keeps it from a 5.

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 core action and scope, followed by the error case and the feature gates. "Get a call" duplicates the title slightly, but nothing else is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description would ideally hint at the returned call object, yet it only documents one error case. For a simple single-resource getter with fully described parameters and annotation coverage, it is adequate but leaves the return value opaque.

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%, with both `id` and `fields` documented in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema, such as where a valid call ID comes from or the cost of narrowing fields.

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 specific verb and resource ("Get a call") and narrows scope with "One call from the history," which implicitly contrasts with the sibling list_call_history. It stops short of naming an alternative explicitly, so it is clear but not fully differentiated.

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 by "one call from the history" and gated by the per-type feature requirements, which tells the agent when the call will fail. There is no explicit when-to-use versus list_call_history or search-style alternatives, and no stated prerequisites about needing the call ID from a prior listing.

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.

Resources