Skip to main content
Glama

get_job

Read-only

Check the status of an analysis or render job, optionally waiting up to 120 seconds for completion instead of polling.

Instructions

Status of an analysis or render job. wait_seconds blocks until it finishes (max 120) — prefer this over polling in a tight loop.

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the non-obvious trait that wait_seconds is a blocking call capped at 120 seconds, which materially changes caller behavior. It does not disclose what happens on a completed or invalid job (timeout semantics, error behavior), leaving a small gap.

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?

Two sentences, both load-bearing: the first establishes purpose, the second establishes the blocking behavior and the preferred usage pattern. Front-loaded and free of filler.

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?

An output schema exists, so return values need not be described, and the blocking behavior is the key non-schema fact. Remaining gaps are minor: no mention of terminal vs in-progress states when the wait times out, and no error-path note for an unknown job_id.

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 carry parameter meaning. It does explain wait_seconds as a blocking wait with a 120 cap, which the schema only implies via maximum/default, but it says nothing about job_id's expected format or source.

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 names the resource (an analysis or render job) and what it returns (status), which is unambiguous against siblings like cancel_job or render_highlight. It stops short of a full verb+resource framing and never explicitly contrasts itself with get_render or a polling alternative beyond the wait_seconds note.

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 clear conditional guidance for one mode: use wait_seconds (max 120) rather than polling in a tight loop. That is actionable and correct, but there is no guidance on when to call get_job at all versus get_render or how to handle non-terminal states if polling outside the block.

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