Skip to main content
Glama

get_job

Read-only

Check the status of a long-running CAD conversion or edit job, including elapsed time, saved outputs, or errors, without making API calls.

Instructions

The state of a long conversion started by convert_drawing or edit_drawing: running (with elapsed seconds), or done with the saved outputs, or the error. Uses no calls.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description does add real behavioral value by disclosing the three return states (running with elapsed seconds, done with saved outputs, error) despite there being no output schema; it does not cover job persistence/expiry or what happens to an unknown job_id.

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 front-loaded sentence that puts the resource and its producers first and the states second. The trailing 'Uses no calls' clause is vague enough to be wasted wording, but overall there is little fat.

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 polling tool with no output schema, the description largely covers what the agent needs, especially the response states. Missing are the polling cadence, job lifetime, and error-on-unknown-id behavior, which matter for a job-status endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for the single job_id parameter. It hints that the id originates from a convert_drawing/edit_drawing call, which is genuinely useful, but it never states the id format, where exactly to obtain it, or how invalid ids are handled.

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?

Names the specific resource (the state of a long conversion job) and ties it to the two producers, convert_drawing and edit_drawing, so the agent can tell it apart from those. It also enumerates the three result states, though it never uses an explicit verb like 'poll' and the final clause 'Uses no calls' is cryptic.

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?

Implicit guidance is clear: this is the follow-up tool to call after starting a conversion with convert_drawing or edit_drawing. However, it never says when to poll, how long to wait between checks, or what to do if a job is still running, so the agent must infer the workflow.

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