repolens
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 |
|---|---|
| packA | Build a deterministic, token-budgeted, AST-aware context pack for a repository path or query and return it with a hash-chained provenance manifest of exactly what was read. |
| verifyC | Verify a provenance manifest (list of rows) is an unbroken hash chain. |
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 2 tools
The two tools have clearly distinct purposes: pack builds a context pack with a provenance manifest, while verify checks the integrity of that manifest. No overlap or ambiguity.
Both tool names are imperative verbs (pack, verify), following a simple and consistent pattern. No mixing of styles or conventions.
With only 2 tools, the set feels thin for a general-purpose server. While the tools are focused, the count is borderline according to calibration guidelines (1-2 tools is considered thin).
The server fully covers its stated purpose: building a context pack with a provenance manifest and verifying the manifest's integrity. There are no obvious gaps for this narrow domain.