Skip to main content
Glama

Get a creation

get_generation
Read-onlyIdempotent

Status (queued, running, completed, failed), progress and, once completed, the download URLs of a creation.

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_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id create_video, create_daily_video or create_image returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing the four possible status values and the fact that download URLs are only present in the completed state, which prevents an agent from treating a 'queued' result as an error.

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?

A single sentence with zero filler, front-loading the status enumeration and then the conditional return of download URLs. Every clause carries information.

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?

With no output schema, the description must carry the return-value burden, and it does so reasonably: status values, progress, and conditional download URLs. It stops short of explaining failure payloads, retry/polling cadence, or whether results are retained, which keeps it from a 5 for a status-polling 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 'id' parameter is already documented in the schema as the id returned by create_video, create_daily_video or create_image. The description adds nothing about the parameter, so the baseline 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 ('a creation') and enumerates exactly what is retrieved: status with its four enumerated states, progress, and download URLs once complete. That distinguishes it well from sibling creation tools like create_video and create_image, though the retrieval verb itself is only implied by the name rather than the description.

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 explicit when-to-use statement, no guidance on polling after a create_* call, and no mention of what to do on 'failed' versus 'queued'. The phrase 'once completed' faintly hints that the tool may be called before completion, but the agent must infer the polling workflow entirely.

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