Skip to main content
Glama
Sign In

CallMCP — Phone Call MCP Server

by ai.callmcp
OverviewDiscussionsAdmin

Get Call Recording

get_call_recording
Read-onlyIdempotent

Get the real call recording URL for a call so reviewers can listen to the voice/audio instead of relying only on the transcript.

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_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
call_idYesThe KaiCalls call ID to get the recording for

Output Schema

NameRequiredDescriptionDefault
callNo
errorNoPresent when success is false
successYesWhether the tool completed successfully
recording_availableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive operation. The description adds that it returns a real recording URL for audio playback, but does not disclose practical details such as URL expiration, authentication requirements, or whether recordings may be missing for some calls.

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?

The description is a single, well-structured sentence with no wasted language. The purpose and primary value are front-loaded.

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?

Given the simple one-parameter read operation, existing annotations, and an output schema, the description is largely complete. It could be improved by noting recording availability or URL freshness, but the core intent is clear.

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?

There is only one parameter, call_id, and the schema description coverage is 100%, so the schema already fully documents it. The description adds no further parameter-level semantics, which is acceptable given the high schema coverage baseline.

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: getting the real call recording URL for a call. It also distinguishes the output from transcript data by emphasizing voice/audio, which differentiates it from the sibling get_transcript tool.

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?

The description gives a clear usage context: reviewers should use it to listen to audio instead of relying only on the transcript. It implies the alternative (transcript) but does not explicitly state when not to use this tool, such as if a recording is unavailable.

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

All CallMCP — Phone Call MCP Server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources