Skip to main content
Glama

get_call

Read-onlyIdempotent

Retrieve call status, duration, cost, and transcript by call ID to analyze AI voice agent performance and track telephony expenses.

Instructions

Get detailed information about a specific call including status, duration, cost, and transcript.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
call_idYesThe call ID

Implementation Reference

  • Registration of the 'get_call' tool with server.registerTool, including name, description, input schema, and handler function
    server.registerTool(
      "get_call",
      {
        description: "Get detailed information about a specific call including status, duration, cost, and transcript.",
        inputSchema: {
          call_id: z.string().describe("The call ID"),
        },
        annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },
      },
      async (params) => callTool(() => client.get(`/calls/${params.call_id}`))
    );
  • Handler function for get_call - executes the API GET request to /calls/{call_id}
    async (params) => callTool(() => client.get(`/calls/${params.call_id}`))
  • Input schema definition for get_call tool using zod - requires call_id string parameter
    {
      description: "Get detailed information about a specific call including status, duration, cost, and transcript.",
      inputSchema: {
        call_id: z.string().describe("The call ID"),
      },
      annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },
    },
  • Helper function callTool that wraps API calls with try-catch error handling and formats results
    async function callTool<T>(fn: () => Promise<T>) {
      try {
        return toolResult(await fn());
      } catch (err) {
        const apiErr = err as ApiError;
        return toolError(`API error (${apiErr.status}): ${apiErr.message}`);
      }
    }
Behavior4/5

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

Annotations cover safety profile (readOnly, idempotent), so description adds value by disclosing return payload contents (status, duration, cost, transcript). This is important given the sibling get_call_transcript tool exists, clarifying this returns transcript among other data.

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?

Single efficient sentence front-loaded with the verb 'Get'. The field enumeration (status, duration, cost, transcript) earns its place by providing specific behavioral expectations. Zero wasted words.

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 simple single-parameter retrieval tool with good annotations, the description is nearly complete. It compensates for the lack of output schema by listing the specific fields returned, though it could mention error behavior if call_id is invalid.

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% with 'call_id' fully described as 'The call ID'. Description reinforces this is for a 'specific call', but adds minimal semantic detail beyond the schema's clear parameter documentation. Baseline 3 appropriate when schema carries the load.

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?

Description uses specific verb 'Get' with resource 'call' and enumerates exact fields returned (status, duration, cost, transcript). It clearly distinguishes from sibling list_calls (which lists multiple) and get_call_transcript (which is narrower in scope).

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?

The phrase 'specific call' implies usage when you have a call ID versus browsing with list_calls, but there is no explicit when-to-use guidance or named alternatives. Sibling differentiation is implicit rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JobXDubai/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server