Skip to main content
Glama

status

Read-only

Compares a repository against a base revision to report what is new or has grown, including measured limits, verification steps, standing debt, change footprint, and unanalysed areas.

Instructions

Returns what is new or has grown in a repository since base: at most five marks, each a measurement with its limit and a way to verify it, then one line each for what is listed in report only, for what the change touched but did not create and for added code without a use, one line of standing debt, one line that counts the standing items the repository acknowledges, the footprint of the changes since base, and what was not analysed.

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": {
      "repository": "<repository>"
    },
    "name": "status"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoThe revision to compare with: a commit, a tag or a branch. When it is not an ancestor of the head, their merge base is used and the answer says so. Without it, the default base the repository declares in .plimsoll.toml is used.
repositoryYesAbsolute path of the repository: its top folder or any folder inside its working tree.

Output Schema

NameRequiredDescriptionDefault
baseYes
headYes
moreYes
marksYes
countsYes
historyYes
touchedYes
versionYes
evidenceNo
questionYes
resolvedYes
sectionsNo
standingYes
detectorsYes
footprintNo
summariesYes
reportOnlyYes
notAnalysedYes
acknowledgedNo
acknowledgedInNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, closed-world, non-idempotent call, so the safety profile is covered. The description adds real behavior beyond that: the merge-base fallback when `base` is not an ancestor (and that the answer discloses it), the .plimsoll.toml default, the cap of at most five marks, and an explicit 'what was not analysed' section that surfaces limitations. It does not explain why the call is non-idempotent despite being read-only, which is the one notable gap.

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

Conciseness2/5

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

The purpose is front-loaded, but everything after the colon is one long run-on enumeration of output sections that is hard to parse and heavily duplicates what the output schema already declares. Sentences do not earn their place individually, and undefined jargon ('marks', 'standing debt') bloats rather than clarifies.

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?

Because an output schema exists, the description did not need to narrate the return shape, yet that is most of its content. The genuinely missing pieces are guidance on choosing between this and report/explain and a plain-language definition of the domain terms. Coverage of parameters and safety is adequate, so it is viable but with clear holes.

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% and both parameters are already well documented, including the merge-base rule and the .plimsoll.toml default, so the schema is doing the heavy lifting. The description references `base` only incidentally and mentions `report`, which is not a parameter at all, adding no usable parameter semantics. Baseline 3 applies.

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 opening clause gives a concrete verb and resource: it returns what is new or has grown in a repository since a given base revision. That is enough to distinguish it from a plain diff or file read. It falls short of 5 because it never positions itself against the sibling tools report and explain, and the terms it leans on ('marks', 'standing debt', 'footprint') are project jargon an agent cannot resolve from the text alone.

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?

There is no statement of when to call this instead of report or explain, nor any prerequisite or cost guidance. The phrase 'what is listed in `report` only' gestures at a related concept but is ambiguous — it is unclear whether `report` is a parameter, a sibling tool, or a config section — so it creates confusion rather than routing guidance.

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

Deploy Server

Other Tools