Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PROJTRUTH_REPONoThe repo the server reads from; defaults to the process cwd. Start the server in the project root, or set this variable in the MCP server config.

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
status_reportA

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.

req_listB

List registered requirements, their criteria count, declared status and file scope.

req_addA

Register a requirement with acceptance criteria. Use when the user states a feature or a promise the project should keep. Criteria are auto-numbered R.; they are what evidence files link to.

req_set_statusA

Declare a requirement's status: pending or implemented. verified, stale and unverified are computed from evidence and are rejected here - write an evidence file instead.

req_scopeA

Restrict a requirement's staleness to specific file globs. Without scope, any source change in the repo marks it stale; with scope, only changes to matching files do.

evidence_scanA

Re-read the evidence folders and index them by criterion id. Sources: .claude/skills/verify-*/evidence/** and .projtruth/evidence/**.

decideA

Append a decision with its reason to the project's decision log. Use when a non-obvious choice is made (library, data model, trade-off) so a later session does not re-litigate it.

decisions_listA

Read the project decision log (newest last) before re-opening a settled question.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 8 tools

Disambiguation4/5

Each tool maps to a distinct resource+action pair: decisions (decide vs decisions_list), requirements (req_add, req_scope, req_set_status, req_list), evidence (evidence_scan), and reporting (status_report). The only mild overlap is req_list vs status_report, but descriptions clarify that one shows declared registration data while the other shows computed status plus evidence. No tool appears to duplicate another.

Naming Consistency3/5

Most tools follow a noun-prefixed grouping convention (req_add, req_scope, req_set_status, req_list, decisions_list, evidence_scan, status_report), which makes the families readable, but the bare verb `decide` breaks the pattern and `req_set_status` mixes noun+verb+noun while `decisions_list` and `status_report` are noun+noun. The set is still understandable but not a single predictable verb_noun scheme.

Tool Count5/5

Eight tools is well within a healthy range and each addresses a distinct part of the requirement/decision/evidence lifecycle. Nothing feels padded or redundant; every tool has a clear role in the workflow.

Completeness3/5

The core lifecycle is covered (capture requirements, scope, set status, read; log and read decisions; scan evidence; report status), but there is no way to update or delete a requirement, remove or amend a decision, or edit criteria after creation. Writing evidence files is implied to happen outside the tool surface, which is a deliberate but notable gap for agent workflows.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues