Skip to main content
Glama

Check a background task

get_task
Read-onlyIdempotent

Check a background task once: a generation, a download, or a video import, analysis, scoring or render.

    Prefer wait_for_task, which polls for you.
    

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": {
      "task_id": "<task_id>"
    },
    "name": "get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNogenerate
task_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false) and open-world scope, so the bar is lower. The description adds genuinely new behavior: this is a single-shot, non-polling check, contrasting with wait_for_task's polling. It does not mention what happens for an unknown or expired task_id, which would round it out.

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 short sentences with zero waste; the core action is front-loaded and the alternative recommendation follows immediately. Nothing is repeated from the schema or annotations.

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-value detail is unnecessary, and the polling-vs-single-check distinction is the key thing an agent needs. The remaining gap is error behavior for invalid or unknown task_id and the relationship between kind and the original submission.

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 carries the burden. It partially compensates by spelling out the kind values in prose (generation, download, import, analysis, scoring, render), but says nothing about task_id, the default kind of "generate", or whether kind must match the original task type.

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?

States a specific verb (check) and resource (a background task), and enumerates the task kinds it covers (generation, download, video import/analysis/scoring/render), which map directly to the kind enum. It also explicitly names the sibling it is not (wait_for_task), so an agent can distinguish the two without opening either 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?

"Prefer wait_for_task, which polls for you" gives an explicit alternative plus the reason (polling) for choosing it. The implied when-to-use for this tool — a single non-blocking check — is clear from "once" but is not stated as a positive condition or exclusion, so it falls short of a full 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.