plimsoll
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| explainA | Returns the evidence behind one mark, computed again: the files and patterns searched, the counts and what was left out. |
| reportA | Returns the full report of a repository against |
| statusB | Returns what is new or has grown in a repository since |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
explain (single-mark evidence drill-down), report (full repository report), and status (delta digest since base) each target a different granularity, and the descriptions make the distinction reasonably clear. The main risk is report vs status, since status returns a capped subset of what report already contains, which could cause an agent to pick the wrong one for a full picture.
All three names are single lowercase words in the same style: explain, report, status. There is no mixing of conventions or verb styles, so the naming is predictable even if it isn't a verb_noun pattern.
Three tools map cleanly onto three views (detail, full, delta) of the same analysis, so each earns its place. It is on the lean side for a measurement/reporting server, but not thin enough to be a mismatch.
The read surface is coherent (run a report, get a delta summary, verify a single mark), but there is no way to manage the baseline itself, list repositories, or acknowledge standing debt items even though report and status reference acknowledged items. These are notable gaps an agent would hit when trying to act on the findings rather than just read them.