Skip to main content
Glama

job_status

Retrieves or refreshes the status of a routed Agent Router job by ID so you can track queued, running, or completed work.

Instructions

Get or refresh one Agent Router job by id.

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

Input Schema

NameRequiredDescriptionDefault
jobIdYes
refreshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not say whether refresh triggers server-side re-execution, cache invalidation, or merely a re-read, nor what a job's state model looks like or whether the call blocks while the job runs.

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 short, front-loaded sentence with no filler; the resource and lookup key come first. Its brevity is efficient, though it edges toward under-specification rather than crisp density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a job-status polling tool with two parameters, no annotations, and no output schema, the description does not explain the refresh flag, the possible job states, or the return shape. An agent can identify the right tool but not confidently invoke it with the correct refresh setting.

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 adds the meaning of jobId as the lookup key, which is helpful, but says nothing about the refresh boolean — the most behaviorally significant parameter — leaving its default and effect undocumented in both places.

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?

States a specific verb pair (get/refresh) and resource (Agent Router job), scoped to "one ... by id", which distinguishes it from the sibling list_jobs. It stops short of naming alternatives explicitly, but the singular lookup purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus list_jobs or route, and no mention of polling cadence or when a caller should prefer status checks over re-invocation. The word "or" between get and refresh leaves the choice between the two modes unexplained.

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