Skip to main content
Glama

Check a generation

get_job
Read-onlyIdempotent

Get the status and result of a generation job by its job_ref (returned by run).

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_ref": "<job_ref>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_refYesthe opaque job_ref returned by the run tool

Output Schema

NameRequiredDescriptionDefault
kindNo
errorNo
modelYes
statusYes
job_refYes
outputsNo
categoryYes
cost_usdNo
thumb_urlNo
output_urlNo
result_textNo
cost_creditsNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that it returns both status and result and that job_ref is opaque, but says nothing about terminal states, behavior on an unknown or expired job_ref, or whether results are retained over time — the traits that matter most for a status-check tool.

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 that front-loads the action and outcome (status and result) and then qualifies the input. Nothing is wasted or buried.

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?

An output schema exists, so return values need no explanation, and the single required parameter is fully documented. The remaining gap is workflow context — how often to poll and how to interpret a non-final status — which an agent calling a job-check tool would benefit from.

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 description coverage is 100% and the single parameter is already documented as 'the opaque job_ref returned by the run tool'. The description repeats that same provenance and opacity information rather than adding new meaning, 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 a specific verb and resource ('Get the status and result of a generation job') and ties the input to its origin ('returned by run'), which implicitly separates this from the sibling that starts a job. It stops short of explicitly contrasting itself with `run`, so it is clear but not maximally differentiated.

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 only implied: the parenthetical '(returned by run)' suggests this is the follow-up call after starting a generation. There is no explicit statement of when to call it versus alternatives, no guidance on repeated polling, and no indication of when a job is considered final.

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