Skip to main content
Glama

Job status

job_status
Read-only

Waits for a job started by another tool that was still running, and returns its download link when it is done.

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_idYesthe id the tool returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations only declare readOnlyHint=true and openWorldHint=false, so the description does the real work by disclosing that this call blocks/waits rather than returning immediately, which is the critical behavioral fact for an agent. It omits equally relevant behavior: how long it waits, whether it times out, and what happens if the job failed, so the disclosure is useful but incomplete.

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?

One sentence, front-loaded with the blocking behavior and followed by the return value; there is no padding or redundancy.

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?

For a one-parameter blocking tool with no output schema, the description covers the essence (waits, then returns a download link). It leaves out failure/timeout outcomes, which are exactly the cases an agent needs in order to recover, so it is adequate rather than complete.

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?

There is a single parameter with full schema description coverage ('the id the tool returned'), so the schema already carries the semantics. The description adds nothing further about job_id format or validity, which is acceptable at 100% coverage but merits only the baseline.

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 uses a specific verb and object ('waits for a job', 'returns its download link') and scopes the tool to jobs 'started by another tool that was still running', which makes it unmistakable against the PDF-manipulation siblings. It stops short of naming the tool that produces the job, so the agent must infer the pairing.

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?

The trigger condition is implied: use this when a previously invoked tool returned a job that was still running. There is no explicit statement about what to do if the job has already finished, whether polling repeatedly is expected, or how to handle failure, leaving the usage decision partially to inference.

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