Skip to main content
Glama

job_status

Check a generation job by ID, including jobs that exceeded the 10-minute wait, and optionally download the completed file to the output folder and return its path.

Instructions

Check a generation job by id (e.g. one that outlived the 10-minute wait).

download: if true and the job is done, save its file to the output folder and return the path.

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": {
      "job_id": "<job_id>"
    },
    "name": "job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
downloadNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose two useful behaviors – the 10-minute wait timeout that motivates the call, and that download=true writes a file to the output folder and returns its path. It omits other behavioral facts an agent needs, such as what job states exist and whether the call must be repeated until completion.

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, front-loaded sentences: the core action first, the optional side effect second. Every line earns its place, though the second sentence reads like a copied schema hint rather than flowing prose.

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?

An output schema exists, so return-value explanation is rightly omitted, and the tool is simple (one required param). Still missing is where the job_id originates (presumably a generate_* response) and how the agent should behave when the job is not yet done, which matters for an async status tool.

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 0%, so the description must compensate. The `download` param is well explained (only acts when the job is done, persists the file, returns the path), which adds real meaning beyond a bare boolean named "Download". `job_id` is left unexplained – the schema only says "Job Id" string – but the leading phrase "check a generation job by id" plus its example gives enough context to supply one, keeping this at a 4 rather than lower.

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 a specific verb and resource ("check a generation job by id") and scopes it with a concrete scenario ("one that outlived the 10-minute wait"), which distinguishes it from the generate_* siblings. It is clear without needing the schema opened, though it doesn't explicitly say it is read-only polling.

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 implied rather than stated: the parenthetical tells the agent this is for jobs that outlived the 10-minute wait, which is a real trigger. There is no explicit when-not guidance, no statement about repeated polling, and no named alternative for other cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.