Skip to main content
Glama

Report progress

taskhold_progress
Idempotent

Move the person's progress bar during a long step or a task without steps: percent, or current and total (e.g. 12 of 40 files), plus a short message about what's happening now. On a task with steps, the steps drive the bar: numbers you send for the task go to its running step. Call at milestones, every few minutes at most. Returns the task's progress bar and, on a task with steps, which step your numbers went to. Fails without percent, total or message, on an unknown task_id, or past the per-minute limit (the error says when to retry).

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

Input Schema

NameRequiredDescriptionDefault
totalNoTotal items
currentNoItems done so far, with total
messageNoWhat is happening now, e.g. "Running the test suite"
percentNo0-100
task_idYesThe ID of the task you are reporting on (a step, or a task without steps)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / task_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations by disclosing failure modes (missing percent/total/message, unknown task_id, per-minute rate limit with a retry hint in the error) and the return shape (progress bar plus which step the numbers hit). It also resolves the non-obvious behavior that on stepped tasks the numbers are redirected to the running step.

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?

Front-loads the core action and keeps every sentence informational, with no filler. It is somewhat dense across five sentences, packing scoping, cadence, return value, and errors together, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still covers the return value, the stepped-task redirection rule, throttling, and the required-input condition. An agent has everything needed to call this correctly and recover from the documented errors.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds the either/or relationship between percent and current+total and gives a concrete example ("12 of 40 files"). It does not explain the maxLength or numeric bounds, which the schema already covers.

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?

Names a specific action on a specific resource: advancing the progress bar with percent or current/total plus a status message. It also clarifies the step-vs-no-step scoping rule, which is what separates it from siblings like taskhold_start, taskhold_complete, or taskhold_update.

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 clear cadence guidance ("Call at milestones, every few minutes at most") and explains which task types accept which numeric form. It never explicitly names an alternative for finishing or blocking work, so the agent must infer that taskhold_complete/block handle those transitions.

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