Skip to main content
Glama

Task status

task_status
Read-onlyIdempotent

Register and update a multi-step task in the tray with current, done, and next steps; mark it done when complete so progress stops and completion is shown.

Instructions

MANDATORY on all multi-step tasks: register and update your current task in the tray (panel block + multi-agent tab + icon tooltip). Call within your first 2 tool calls with status: 'running', update every 3–5 calls so current, done and next always match reality, and when the task is complete MUST call with status: 'done' so the tray marks the task as completed (green check, stops progress animation) instead of leaving it looking like it is still running.

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": {
      "title": "<title>"
    },
    "name": "task_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
doneNo
nextNo
noteNoShort human-readable explanation (1 line, in the user's language) of what you are about to do and why. Shown to the user on the approval card. Always provide when calling mutating tools.
agentNo
titleYes
statusNoTask state: 'running' while in progress, 'done' when completed (turns card green & stops spinner), 'waiting' when waiting on owner.
currentNo
startedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: it discloses where the state is rendered and the concrete effect of 'done' (green check, stops the progress animation) versus leaving the task looking active. There is mild tension with readOnlyHint=true, since the call visibly mutates tray state, but the description is transparent about what changes, so it is not a genuine contradiction.

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 hard requirement ('MANDATORY') before the mechanics, and every clause carries actionable information about cadence or state effects. It is a single very dense sentence, but nothing is redundant.

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 an 8-parameter, 25%-coverage tool with no output schema, the description covers the workflow and the three list fields well but leaves 'agent', 'startedAt' and 'title' semantics unexplained. It is sufficient to invoke correctly in the common case but not complete for the full schema.

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?

With only 25% schema description coverage, the description does compensate for the important fields by explaining that 'current', 'done' and 'next' must 'always match reality' and by spelling out the required 'running'/'done' status lifecycle in prose. It adds nothing for 'agent', 'startedAt', or 'note', so half the undocumented parameters remain opaque.

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?

Uses a specific verb+resource pair ('register and update your current task in the tray') and even names the surfaces it affects (panel block, multi-agent tab, icon tooltip). It is clearly distinguishable from a job-output/job_status style tool, though it never explicitly contrasts itself with the sibling 'job_status'.

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 unusually concrete when-to-use guidance: mandatory on multi-step tasks, call within the first 2 tool calls with status 'running', refresh every 3-5 calls, and MUST call with status 'done' at completion. No exclusions or named alternative tools are given, which keeps it just short of a 5.

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