Skip to main content
Glama

Wait for jobs

wait_for_jobs
Read-only

Poll until every job finishes or timeout_seconds passes, then report. Images take ~20-40s, videos ~2-3 min; call again if all_finished is false.

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": "wait_for_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_tokensYesjob_token values from generate_assets
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the meaningful behavior — this call blocks/polls up to a timeout, and returns an all_finished flag the caller must inspect. The duration estimates are genuinely useful planning context absent from structured fields.

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 dense sentences, front-loaded with the behavior and followed by the actionable timing data and retry rule. No 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?

For a 2-parameter polling tool with no output schema, the description covers blocking semantics, timeout meaning, and the one response field that drives the agent's next action (all_finished). Minor gap: 'report' leaves the rest of the return payload unspecified.

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 50%: job_tokens is documented in the schema (source: generate_assets) while timeout_seconds has only bounds and a default. The description explains what the timeout does in prose and the timing hints imply sensible values, but adds no explicit guidance on choosing timeout_seconds. Baseline 3 is appropriate.

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 and resource: 'poll until every job finishes or timeout_seconds passes, then report.' That clearly separates it from passive status reads, though it never names check_jobs or cancel_job to sharpen the boundary.

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?

Gives concrete re-invocation guidance ('call again if all_finished is false') and expected durations per media type (images ~20-40s, videos ~2-3 min) that inform timeout selection. It stops short of stating when to prefer a non-blocking status tool over waiting.

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