Skip to main content
Glama

Job status

get_job
Read-only

Status of a generation by job_id: running, done (with the picture or video link) or failed (credits refunded). wait_seconds (0–50) waits for it to finish. Free.

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": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
wait_secondsNo

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 only declare readOnlyHint and openWorldHint=false; the description adds real behavioral context beyond that: the three terminal states, the fact that failures refund credits, and that the call is free. It omits polling/rate expectations and whether results expire, but the failure-refund guarantee is the kind of consequence an agent needs.

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 tightly packed sentences plus the fragment "Free." with status outcomes front-loaded after the core purpose. The trailing "Free." earns its place as cost context, though as a bare fragment it is slightly ambiguous about what exactly is free.

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-only polling tool with no output schema, the description covers states, cost, and wait semantics — enough for an agent to call it correctly. The main missing piece is what happens with no wait_seconds and whether a job_id remains queryable after completion.

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 0%, so the description must carry parameter meaning; it explains that wait_seconds (0–50) waits for completion but not the default behavior when omitted, and job_id's meaning is mostly restated from the name. Adequate but with a clear gap around the default/blocking semantics.

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

Purpose5/5

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

States a specific verb+resource ("Status of a generation by job_id") and enumerates the exact outcome states: running, done with a picture or video link, failed with credits refunded. This makes it immediately distinguishable from generate_* and list_generations siblings.

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: "wait_seconds (0–50) waits for it to finish" hints at the poll-after-generate pattern, but the description never says when to call this versus list_generations, nor what to do if no wait_seconds is supplied (immediate return vs blocking).

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