Skip to main content
Glama

Spoof Caller ID

Text-to-speech call status

get_tts_call
Read-onlyIdempotent

Status, duration and cost of a text-to-speech call by its ref. Free.

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": {
      "ref": "<ref>"
    },
    "name": "get_tts_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesThe ref returned by tts_call

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds two things beyond that: the fields actually returned (status, duration, cost) and the fact that the call is free, which matters for polling decisions. It stops short of describing status values or whether the record persists indefinitely.

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?

One short sentence with the resource and returned fields front-loaded, followed by a one-word cost note. Nothing is wasted, though the telegraphic noun-phrase style ('Status, duration and cost of...') and the dangling 'Free.' fragment read as compressed rather than polished.

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?

For a single-parameter read tool whose annotations fully cover the safety profile and whose parameter is fully documented in the schema, the description supplies the missing piece: what the response contains. No output schema exists, so naming status, duration and cost is exactly the compensating detail an agent needs.

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?

With a single parameter at 100% schema description coverage, the schema already explains that ref is the value returned by tts_call, including its 16-hex-character pattern. The description's 'by its ref' restates rather than extends that, so 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?

Names a specific resource (text-to-speech call) and the exact fields returned (status, duration, cost) plus the lookup key (ref), so the verb/resource pair is unambiguous. It does not distinguish itself from the sibling get_call, which retrieves status for non-TTS calls, leaving an agent to infer the split from the name alone.

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 'by its ref' plus the schema note that ref is 'returned by tts_call' implies this is the follow-up polling call after initiating a TTS call. There is no explicit when-to-use statement, no exclusion versus get_call, and no guidance on how often to poll or whether status is terminal.

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.

Resources