Skip to main content
Glama

Get a conversion

get_conversion
Read-onlyIdempotent

The status of a conversion by id, with its download link once done. Waits up to waitSeconds (at most 100) for it to finish.

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": {
      "id": "<id>"
    },
    "name": "get_conversion"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe conversion id
waitSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral context: the call blocks for up to waitSeconds with a hard cap of 100, and the payload evolves to include a download link once the conversion completes.

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?

Two short sentences, no filler, and the core purpose is front-loaded ahead of the blocking-time caveat. Every clause carries information an agent needs to call the tool.

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?

For a two-parameter read tool with no output schema, the description covers what is returned (status plus eventual download link) and the wait semantics. It stops short of describing possible status values or the timeout outcome, which would help an agent decide whether to re-poll.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% — id is documented in the schema but waitSeconds carries only bounds. The description supplies the missing meaning: waitSeconds is a blocking wait duration for job completion, capped at 100. That compensates for the schema gap, though it doesn't say what happens on timeout.

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+resource: retrieve the status of a conversion by id, and adds that a download link appears once done. This cleanly separates it from convert (start a job) and confirm_conversion, though it never names a sibling explicitly.

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 polling/blocking intent is implied by 'Waits up to waitSeconds ... for it to finish', which tells an agent how to use the wait parameter. There is no explicit guidance on when to poll without waiting versus blocking, nor any named alternative to use instead.

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.