Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 base: all marks, all measured numbers with their values at base, the standing debt item by item, the standing items the repository acknowledges, the footprint of the changes since base, and what was not analysed.

statusB

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 3 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness3/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues