Skip to main content
Glama

status_report

Reports every requirement's computed status—verified, stale, unverified, or pending—with supporting evidence, so you can determine what is done, what remains, or whether a feature is finished.

Instructions

Where the project actually stands: every requirement with its computed status (verified/stale/unverified/pending) and the evidence behind it. Call this first when asked what is done, what is left, or whether a feature is really finished. Pass changed_since to narrow it to what a branch or PR touches.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "status_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
changed_sinceNogit ref (e.g. origin/main); report only requirements touched by changes since it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.1
    • addedInput schema / properties / changed_since
      Added value: +{
      +  "description": "git ref (e.g. origin/main); report only requirements touched by changes since it",
      +  "type": "string"
      +}
  2. First observedv1.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that statuses are computed and evidence is included, and the term 'report' implies a read-only operation, but it does not explicitly state side-effect safety, authentication needs, or freshness/pagination behavior.

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?

The definition is three sentences, front-loaded with the core output and followed by the selection guidance and the optional narrowing parameter. Every sentence adds distinct value with no repetitive or filler language.

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 single optional-parameter read tool with no output schema, the description covers the resource, the status values, the evidence, the primary use cases, and the param's intent. It is nearly complete, with only explicit read-only/behavioral guarantees missing.

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?

The schema already documents changed_since at 100% coverage, so the baseline is 3. The description adds useful intent by explaining that it narrows the report to what a branch or PR touches, which is more actionable than the schema's raw git-ref wording.

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 states a specific resource and output: every requirement with its computed status and supporting evidence. It distinguishes itself from a plain requirement listing by emphasizing computed status and evidence, and it signals a first-call role relative to evidence-oriented siblings.

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?

It gives clear triggering contexts: questions about what is done, what is left, or whether a feature is really finished, plus the explicit instruction to call it first. It does not name an alternative or state when not to use it, but the guidance is strong enough to select the tool confidently.

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