Skip to main content
Glama

Get generation

get_generation
Read-only

Current status and outputs of a generation.

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": {
      "generation_id": "<generation_id>"
    },
    "name": "get_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
generation_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without the description's help. The description adds nothing beyond a restatement of the resource: it does not say whether the call blocks, whether it is safe to poll repeatedly, what lifecycle states exist, or what happens if the generation has failed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with no padding, so there is no wasted prose. However, it is concise by virtue of under-specification rather than tight writing: there is no verb, no object framing, and no structure to front-load.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be documented. But for a status-retrieval tool in a set containing wait_for_generation and cancel_generation, the description should convey polling semantics and the distinction from those siblings; neither is present.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter generation_id, and the description does not explain it or say where the ID comes from (e.g., returned by generate). The name is largely self-explanatory, which keeps this from a 1, but the description contributes no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment "Current status and outputs of a generation" names the resource and roughly what it returns, but supplies no verb (get? poll? stream?) and does not distinguish it from siblings like list_generations or wait_for_generation. An agent can guess it is a per-ID status read, but only by inferring from the tool name.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusion of alternatives, and no mention of the obvious counterpart wait_for_generation. The agent is left to infer that this is a non-blocking poll versus a blocking wait, which is exactly the decision that matters here.

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