Skip to main content
Glama
Smitline: AI Phone Calls & Meetings

Smitline: AI Phone Calls & Meetings

Get call details

get_call
Read-only

Fetch a single phone call or meeting by ID to check its current status, final result, transcript, and cost without waiting for completion.

Instructions

Get one phone call or meeting and its current status, without waiting: queued, connecting, ringing, waiting, in_progress, summarizing, then completed, failed, or canceled. A meeting joined by its link may stay connecting for a minute or two on a hosted service, while a machine starts for it; a new room starts in seconds. A finished call includes its result (outcome, summary, details, transcript) and what it cost: cost, at your providers' prices, when self-hosted; on a hosted service such as Smitline Cloud, charge, what the service billed for the call. Errors with not_found for an unknown call id. To wait for a call to finish, use wait_for_call instead; to find call ids, use list_calls.

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

Input Schema

NameRequiredDescriptionDefault
callIdYesCall id returned by start_call, such as call-0123456789abcdef

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint=false, so the description carries the real burden and does well: it enumerates the status lifecycle, warns that hosted meetings can sit in "connecting" for a minute or two while a new room starts in seconds, and specifies that finished calls return result fields plus cost or charge depending on deployment. The one gap is that it never states whether repeated polling is expected or whether any caching/staleness applies, but the operational context given far exceeds the annotations.

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?

The definition is front-loaded with the action and status list, then latency expectations, then return shape, then siblings — a sensible order. It runs long for one parameter, and the nine-state enumeration plus the cost-vs-charge explanation could be tightened, but each sentence carries information an agent would otherwise have to guess.

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?

There is no output schema, so the description must explain return values and does: result (outcome, summary, details, transcript) and the cost/charge distinction on finish. Combined with the not_found error note and the status lifecycle, an agent has everything needed to call and interpret this tool.

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% and the single callId parameter is already documented in the schema as coming from start_call. The description adds no format or sourcing detail beyond that, so the baseline 3 applies — the schema does the work here.

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?

The opening clause names a specific verb and resource ("Get one phone call or meeting and its current status") and immediately scopes it as non-blocking ("without waiting"), which separates it from the sibling wait_for_call. An agent can identify the tool's job without reading the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The final sentence gives explicit routing: "To wait for a call to finish, use wait_for_call instead; to find call ids, use list_calls." That covers both when to use this tool and which alternatives handle the adjacent needs, with the condition that selects each.

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