Skip to main content
Glama

body_task_status

Tracks a background task's progress by reporting completed steps, percent complete, elapsed time, and last evidence so agents can monitor status without guessing.

Instructions

Progress of a background task: steps done, percent, elapsed, last evidence.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "body_task_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the returned fields (steps, percent, elapsed, last evidence), which partially compensates for the missing output schema. However it says nothing about read-only safety, behavior for unknown or completed tasks, or what 'last evidence' means in practice.

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 dense fragment with no filler, and the return fields are front-loaded. It reads as a label rather than a sentence, but nothing in it is wasted.

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 simple read tool with no annotations and no output schema, the enumerated return fields cover the essentials of what comes back. The gap is the task_id contract including its empty default, which an agent needs in order to call it correctly.

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 coverage is 0% for the single task_id parameter, and the schema shows a default of empty string with no explanation. The description never mentions task_id or what an omitted value does (presumably all tasks, or an error), so the most consequential parameter semantic is left unnamed.

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 a specific resource (progress of a background task) and enumerates the returned measures (steps done, percent, elapsed, last evidence), which distinguishes it from body_task_start and body_task_cancel by name alone. It's written as a noun phrase rather than a verb, but the resource is unambiguous.

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?

'Progress of a background task' implies the reading/polling use case, but there is no explicit when-to-use guidance, no mention of polling cadence, and no routing to siblings like body_task_cancel or body_status. The agent must infer that this is the read-only counterpart to task_start.

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