Skip to main content
Glama

set_task_progress

Idempotent

Sets a task's progress percentage from 0 to 99, keeping board status current. Use the task completion tool instead when the work reaches 100%.

Instructions

Set a task's progress percentage (0-99). For 100 use complete_task: in the web app 100% means done, and it asks before completing.

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>",
      "percent": "<percent>"
    },
    "name": "set_task_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
percentYes
task_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare idempotent, non-destructive, non-read-only, open-world. The description adds valuable behavior beyond them: the 0-99 cap and the reason for it (100 triggers a completion confirmation in the web UI). It does not state what happens to dependent fields or the response, but the cap rationale is real added context.

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, front-loaded with the action and the range, then the exclusion and its rationale. No redundant restatement of the name or title.

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 values need not be explained, and annotations cover the safety profile. The only remaining gap is that 'task_id' provenance is unstated, which is minor for an obvious identifier parameter.

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 must carry parameter meaning. It adds the 0-99 constraint on 'percent' that the bare 'integer' type does not convey, but says nothing about 'task_id' format or where to obtain it. Partial compensation warrants a mid score.

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+resource ('Set a task's progress percentage') plus an explicit numeric domain (0-99). It also names the sibling that handles the excluded case (complete_task), so the agent can distinguish it from alternatives without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the boundary case: 'For 100 use complete_task', and explains why (in the web app 100% means done and it asks before completing). That is a concrete when-to-use-this-vs-alternative rule rather than implied usage.

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