Skip to main content
Glama

job_status

Retrieve the receipt of a delegated job or batch, waiting up to a set number of seconds if it is still running, so you can confirm completion and results.

Instructions

Receipt of a delegated job or batch, waiting up to wait_seconds if it is still running.

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
wait_secondsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.1

TDQS

B3.1/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 behavioral burden and does disclose the key trait: the call blocks, waiting up to wait_seconds while the job is still running. It does not state what is returned or how the tool behaves when the wait expires, whether the job failed, or whether job_id is unknown — gaps that matter for a blocking tool.

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?

A single tight sentence with no filler, and the blocking caveat is placed where it will be read. Slightly weakened by the awkward nominal phrasing "Receipt of" instead of a direct verb.

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 values need not be described. Still, for a two-parameter blocking job tool with zero annotation and schema-description coverage, the definition omits timeout/terminal-state behavior and any routing versus sibling job_* tools.

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 0%, so the description must compensate. It does explain wait_seconds meaningfully (an upper bound on blocking time while running), which is real added value, but job_id is left unexplained beyond "delegated job" and the default/units context of wait_seconds is not elaborated.

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?

"Receipt of a delegated job or batch" identifies the resource (a job previously delegated) but uses a nominalized, unusual verb; it is not fully clear whether this returns a status snapshot, a final result, or a log. It does connect implicitly to the delegation workflow, which helps distinguish it from siblings like job_rollback or job_diff, but the core action is only inferred.

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 phrase "delegated job" signals this is called after delegate/delegate_many to collect an outcome. There is no explicit when-to-use rule, no guidance on choosing it over job_continue or job_feedback, and no note on repeated polling.

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