LobbyStack

Get a call with transcript

get_call

Read-onlyIdempotent

Returns one call with its full transcript, in order. Transcripts removed by the retention policy come back empty.

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

Name	Required	Description	Default
`call_id`	Yes	The call id (UUID).

Output Schema

Name	Required	Description
`id`	Yes	Stable identifier (UUID).
`status`	Yes
`channel`	Yes	phone: a phone call. web: a browser call from the website or dashboard.
`outcome`	Yes	answered_by_team: a staff member took the call through Staff answers first.
`summary`	Yes	Short summary of the call, when one is available.
`agent_id`	Yes	The agent that answered. It may be archived, so GET /agents no longer lists it. Null for a call saved before the business had agents.
`ended_at`	Yes
`contact_id`	Yes
`created_at`	Yes	ISO 8601 timestamp in UTC.
`end_reason`	Yes	Why the call ended, as reported by the call provider or receptionist.
`started_at`	Yes	ISO 8601 timestamp in UTC.
`transcript`	Yes
`caller_name`	Yes
`caller_phone`	Yes
`duration_seconds`	Yes
`recording_available`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered upstream. The description does add genuinely useful behavior beyond them: transcripts purged by retention policy return empty rather than failing, which prevents an agent from misreading an empty result. That single caveat is the only extra behavioral context, so it lands above baseline but not high.

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?

Two short sentences, front-loaded with the return contract followed by the retention edge case. Nothing is wasted, though the retention sentence could have been tied more directly to what the caller should do.

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?

Output schema exists so return shape needn't be explained, and the one parameter is fully documented. However, for a fetch-by-id tool the description omits what happens on an unknown or deleted call_id versus a retention-purged transcript — a distinction that matters given it already raised the empty-transcript case.

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 a single required parameter at 100% schema description coverage, so the schema fully documents call_id including its UUID format and pattern. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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 ('Returns one call with its full transcript, in order') and the singular 'one call' implicitly contrasts with list_calls in the sibling set. It does not explicitly name a sibling, so it stops short of a 5.

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?

Use is implied — fetch a single call by id — but there is no explicit statement of when to prefer this over list_calls or another retrieval path, and no prerequisites or error expectations are given.

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

All LobbyStack tools Inspect

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

Need Help?