Skip to main content
Glama

Call status / log

call_status
Read-onlyIdempotent

The log and status of one call. Takes a call's unique id (call_id) or, for a call cpass itself logged, its numeric row_id.

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": "call_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
callIdYesThe call's unique id (call_id), or its numeric row_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / callId / description
      Previous value: -"The call_id (unique id) from call_list, or its numeric row_id"New value: +"The call's unique id (call_id), or its numeric row_id"
  2. First observed

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, non-destructive, and closed-world, so the safety profile needs no restating. The description adds genuine value with the row_id caveat — that the numeric row_id only works for calls logged by this system itself — but it does not say what the returned log contains or how invalid/unknown ids behave.

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 resource and followed by the identifier form. Minor awkwardness in 'a call cpass itself logged' costs a little, but there is no filler.

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?

With one fully described parameter and complete read-only annotations, the essentials are covered. However, there is no output schema, and 'log and status' is left undefined, so an agent cannot anticipate the shape or depth of the response before calling.

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% and the description's phrasing about call_id versus numeric row_id closely mirrors the schema's own parameter description, adding no new syntax, format, or precedence rules. With the schema doing the work, the baseline of 3 applies.

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?

The description names the resource clearly: the log and status of a single call, addressed by identifier. That distinguishes it from the list/aggregate siblings such as call_list, but it does not differentiate from adjacent per-call resources like call_summary, call_transcript, or call_outcome, so an agent must infer which per-call view it needs.

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 only implied: the agent can infer this is for looking up one known call, versus call_list for enumeration. There is no explicit when-to-use statement, no note on when to prefer call_summary, call_transcript, or call_outcome, and no mention of what happens with an unknown id.

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.