drp-compliance
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRP_NO_TELEMETRY | No | Set to 1 to opt out of anonymized telemetry transmission |
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 |
|---|---|
| verify_documentA | Verify a financial document against the DRP-2026 compliance framework. Performs SOX-302 checks and generates a tamper-evident audit trail. |
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 1 tool
With only one tool, there is no possibility of confusion between tools. The tool has a distinct purpose.
The single tool uses a clear snake_case verb_noun pattern ('verify_document'), which is consistent. No other tools exist to create inconsistency.
One tool for a compliance framework is too few. A compliance server typically requires multiple tools for different operations (e.g., listing requirements, checking history), making the scope feel thin.
The tool surface is severely limited. Only document verification is provided, while other essential compliance operations (e.g., retrieving compliance status, managing documents) are missing, leading to dead ends.