Skip to main content
Glama

report_progress

Report progress updates for agent tasks and status changes. Send status, task, milestone, error, or completion messages with optional task tracking and broadcast to rooms.

Instructions

Report progress updates for agent tasks and status changes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentIdYesID of the agent reporting progress. Must be a valid agent ID that exists in the system.
repositoryPathYesPath to the repository or project directory. Can be relative (e.g., '.') or absolute path.
progressTypeYesType of progress being reported: 'status' for general agent status updates, 'task' for task-specific progress, 'milestone' for significant achievements, 'error' for reporting errors/failures, 'completion' for task completion.
messageYesHuman-readable progress message describing what the agent is doing or has accomplished. This message will be displayed in logs and can be broadcast to rooms.
taskIdNoOptional ID of the specific task being reported on. Required when progressType is 'task', 'error', or 'completion'. Used to update task status and progress.
progressPercentageNoOptional progress percentage (0-100) for task completion. Used with progressType 'task' to track completion progress. Will be validated and capped to 0-100 range.
resultsNoOptional key-value pairs of task results or metadata. Used with progressType 'completion' to store task outcomes and artifacts.
errorNoOptional error message when progressType is 'error'. Provides detailed error information for debugging and failure analysis.
roomIdNoOptional room ID to broadcast progress to. If not provided, will use the agent's assigned room from metadata.
broadcastToRoomNoWhether to broadcast this progress update to the agent's assigned room. Defaults to true. Set to false for internal progress tracking only.
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It fails to mention side effects or actions beyond reporting, such as broadcasting to rooms or updating task statuses. The schema hints at these but the description does not confirm or elaborate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but lacks necessary detail. It does not waste words, but it also does not fully inform. It could be expanded without harming conciseness.

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

Completeness2/5

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

Given the tool has 10 parameters, no output schema, and no annotations, the description is too brief. It fails to explain key aspects like valid progress types, broadcast behavior, and when optional fields like taskId are required.

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 100%, so baseline is 3. The description does not add any parameter-specific meaning beyond what the schema already provides. It is acceptable but does not enhance understanding.

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?

The description clearly states the tool's purpose: reporting progress updates for agent tasks and status changes. It uses a specific verb ('report') and resource ('progress updates for agent tasks and status changes'), and is distinct from sibling tools like create_task or list_agents, which have different functions.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or when not to use it, leaving the agent to infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ZachHandley/ZMCPTools'

If you have feedback or need assistance with the MCP directory API, please join our Discord server