Skip to main content
Glama

progress

Sends a brief status note for a given request to keep the sender informed during long tasks. Call at task start and periodically; final answers go through reply.

Instructions

Say you are working on a request addressed to you (not final, nobody is woken): track and wait_reply show it to the sender. Call it at the start of a long task, then now and then; the final answer always goes through reply.

Args: id: request id. note: where you stand, in one sentence (500 characters max).

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": {
      "id": "<id>",
      "note": "<note>"
    },
    "name": "progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
noteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.7
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "progressOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent write; the description is consistent and adds real context beyond them: the note is 'not final, nobody is woken' and becomes visible to the sender via track/wait_reply. That visibility/notification semantics is the key behavioral fact and is not derivable from the annotations. It stops short of saying whether notes are overwritten or appended, which matters for a non-idempotent call.

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?

Purpose, timing, and the reply exclusion are front-loaded in two short sentences, followed by a compact args block. The prose is slightly colloquial but nothing is redundant; every clause carries either routing or parameter information.

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 write with no output schema and annotations covering the safety profile, the description supplies purpose, timing, recipient visibility, and the note length limit. Remaining gaps (append vs. overwrite, error behavior on a bad id) are modest but real for a non-idempotent mutation.

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 0%, so the description carries the burden and mostly does: `note` is defined as 'where you stand, in one sentence' with a 500-character cap that appears nowhere in the schema, and `id` is identified as the request id. The `id` explanation is thin (no format or source), which keeps this from a 5.

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 states a specific action: post a non-final progress note on a request addressed to you. It also distinguishes this from siblings by naming reply (final answer) and track/wait_reply (what surfaces the note to the sender). The opening phrasing ('Say you are working on a request') is slightly indirect, but the effect 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 Guidelines5/5

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

Explicit timing is given ('at the start of a long task, then now and then') plus an explicit exclusion ('the final answer always goes through reply'). The agent knows both when to call this and which sibling to use instead when the message is final.

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