Skip to main content
Glama

Get a job

get_job
Read-only

Use this when an earlier call answered with a job, to see whether it is still running, how far it got, what it found and what it charged. Its status is refreshed every 15 seconds at most, so wait at least that long between reads. A finished people enrichment lists each person's result in the order they were sent; a list enrichment saves what it finds on the list's rows instead. 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": {
      "jobId": "<jobId>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe job's id, as the call that started it answered.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations it discloses things an agent could not otherwise know: results are refreshed at most every 15 seconds, a finished people enrichment returns each person's result in submission order, a list enrichment instead writes onto the list's rows, and calls are free. These are the exact behavioral traits that govern polling loops and result handling.

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?

Three sentences, each doing distinct work: trigger, polling cadence, result semantics per enrichment type, plus cost. The trigger is front-loaded and there is no restatement of the tool name or title.

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?

With no output schema, the description carries the return-value meaning and does so well by distinguishing per-person results from row-level writes, and by flagging cost. It stops short of describing what a failed or cancelled job returns, which is the one gap for a polling tool.

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 jobId already carries its own description and 24-character hex pattern; the description adds no format, provenance, or error semantics for the id. Baseline 3 is appropriate since the schema does the work.

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?

The description opens with a specific trigger and resource: 'Use this when an earlier call answered with a job, to see whether it is still running, how far it got, what it found and what it charged.' It names the exact questions the tool answers (status, progress, results, cost), which distinguishes it cleanly from the cancel/mutate siblings without opening a schema.

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

Usage Guidelines4/5

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

It gives a precise precondition — a prior call returned a job — and an operational constraint: poll no more often than the 15-second refresh interval. It does not name any alternative tool or state when not to use it (e.g. after completion, or to stop a job), which keeps it short of a 5.

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