Skip to main content
Glama

Check jobs

check_jobs
Read-only

Current status of jobs. Completed images include output_url (raw) and composed_url (finished, with brand overlay).

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_tokens": "<job_tokens>"
    },
    "name": "check_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_tokensYesjob_token values from generate_assets

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?

Annotations declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds useful return-shape context (raw vs composed URL for completed jobs) but doesn't disclose behavior for pending/failed jobs, pagination, or whether tokens can be unknown or expired — a meaningful gap for a status tool.

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 compact sentences, front-loaded with purpose and followed by the key output distinction. No wasted wording.

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?

No output schema exists, so the description must carry return semantics; it partially does by naming output_url and composed_url for completed jobs, but omits status values, failure cases, and batch behavior for up to 10 tokens. Adequate but incomplete 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 coverage is 100% and the single job_tokens parameter is documented as coming from generate_assets, with minItems 1 and maxItems 10. The description adds nothing beyond the schema about the tokens; baseline 3 applies.

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 resource (jobs) and the outcome (current status), plus what completed jobs return (output_url raw, composed_url finished). It is clear it is a status-check tool, though it doesn't explicitly contrast with wait_for_jobs or get_render.

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?

Usage is implied: check current status of jobs by token. There is no explicit when-to-use versus wait_for_jobs (blocking wait) or get_render, so an agent must infer the polling-vs-waiting distinction.

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