Skip to main content
Glama

change_status

Read-only

Get compact status and review counts for a change, including paged evidence or delta specs and a closeout preview, while reusing a known revision to avoid unnecessary reloads.

Instructions

Compact planning/task status and review counts. Evidence is unassessed; validation and checked tasks never trigger archive. Reuse knownRevision. Follow evidence/deltaSpecs pages using section and cursor, or preview closeout for exact details.

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

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo
cursorNo
sectionNo
knownRevisionNo
workspacePathNoTrusted absolute project path from this chat; pass on every call. null selects personal storage. Omission uses only the environment default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered, and the description still earns credit by adding non-obvious rules: evidence is unassessed, validation and checked tasks never trigger archive, and knownRevision should be reused. These are genuine behavioral constraints an agent could not derive from the schema. It stops short of describing the response shape or what 'compact' truncates.

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?

It is short (four clauses) and front-loads the output summary, which is good. But it reads as compressed jargon with semicolon-joined caveats, and the opening clause is ambiguous enough that the agent must re-read it to confirm this is a read. Some of that density costs clarity rather than saving space.

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 a read-only, six-parameter tool with no output schema, the definition covers safety, paging, revision reuse, and one archive-related edge case. What is missing is what the agent actually receives (a counts summary?) and how limit interacts with the section/cursor paging. Adequate to invoke, thin for predicting results.

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 17% – only workspacePath is documented structurally – so the description must carry the rest. It does meaningfully explain three of the six parameters: section (with its evidence/deltaSpecs values), cursor for paging, and knownRevision reuse. It says nothing about id or limit (1-100), so the compensation is partial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description frames the tool as returning a 'compact planning/task status and review counts', which reads as a read-side summary rather than the mutation the name change_status implies. That phrase is workable but vague about what a 'status' payload contains and what the 'review counts' are. It never distinguishes itself from read_change or list_changes, leaving the agent to guess the boundary by name alone.

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

Usage Guidelines3/5

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

It gives procedural routing: follow evidence/deltaSpecs pages via section and cursor, or 'preview closeout for exact details'. That tells the agent how to dig deeper once it has committed to this tool. It never states when to call change_status instead of read_change or a list tool, so the selection guidance is only implied.

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