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
prumo_checkA

Checks the context files a coding agent reads (CLAUDE.md, AGENTS.md, SKILL.md, .cursor/rules and the rest) against the git index of a repository. Reports paths whose letter case disagrees with git, broken [[wikilinks]], markdown links and heading anchors, paths that no longer exist, commands naming a script or target no package.json, Makefile or composer.json defines, agent configuration that points at nothing (a rule whose globs match no file, a skill without a description, an MCP server or a hook naming a missing script), and notes an index never mentions. Findings recorded in a .prumo-baseline.json at the repository root are held back and counted in stats.baselined. Nothing is written.

prumo_fixA

Rewrites case mismatches in place to the spelling the git index holds, and a missing path or a markdown link to the name git recorded when it renamed the file, then reports what remains. Nothing else is touched: a link suggested from a name, a missing path with no history and a deleted file are never edited.

prumo_driftA

Reports which sections of the context files describe code that changed after the section was last written: for every section that cites a file or a folder the repository has, when the section last changed according to git blame, how many of the files it cites changed since, and how many commits touched them. Sections come back ordered, the most moved first. It is a reading order for a review, never a finding: a section whose files changed may still be right. Nothing is written.

prumo_budgetA

Reports what each context file costs the agent that reads it at every session: bytes, lines, words and an estimate of tokens at four characters each, largest first; how much each grew since an earlier commit, the one thirty days ago unless since names another; and the paragraphs of twelve words or more written in two places. It measures and counts; nothing here is a finding. Nothing is written.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a distinct responsibility: check audits, fix repairs safe path/link issues, drift measures staleness, and budget measures size. There is no real overlap; check/fix are clearly read vs. write counterparts.

Naming Consistency5/5

All tools follow the same prumo_ prefix with a single lowercase operation word, giving the set a uniform and predictable command surface. The names are short and consistently formatted.

Tool Count5/5

Four tools is well-scoped for a focused context-file health server; each tool earns its place. The set is neither too thin nor overloaded.

Completeness4/5

The core lifecycle of audit, safe repair, drift review, and cost measurement is well covered. The main gap is that prumo_fix only handles a subset of the findings prumo_check reports, leaving broken wikilinks, dead commands, and dangling agent config to manual fixes.

Maintenance

ActivityMaintained
ResponsivenessNo issues