protocol.mcp_server
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ewp_warrant_nowB | Evaluate an EvidenceView (inline or stored) at evaluated_at. Returns the five normative axes. Does not persist warrant. |
| ewp_evidence_view_putA | Persist an EvidenceView. Refuses WarrantView bodies. Trusted origins require ingest_attestation=true. |
| ewp_evidence_view_getC | Load a stored EvidenceView by proposition_id. |
| ewp_check_recordC | Append a VerificationCheck to a stored view. Trusted origin requires ingest_attestation. |
| ewp_evidence_recordC | Append an EvidenceItem to a stored view. |
| ewp_may_actC | Separate action gate. Requires an action object. Will not infer permission from WarrantView alone. |
| ewp_memory_contextC | Bounded packet: axes, evidence ids, warnings. Not a persona biography. OPEN and DEGRADED are explicit. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| EWP protocol identity |
TDQS
Scored across 7 tools
Each tool targets a distinct operation, and descriptions clarify differences (view persistence, appending evidence vs checks, warrant evaluation, action gating, context packet). 'ewp_check_record' and 'ewp_evidence_record' can sound similar, and 'warrant_now'/'may_act' need careful reading, but the boundaries are clear enough for an agent.
All names share the ewp_ prefix and snake_case, which is helpful, but there is no consistent verb_noun pattern: ewp_evidence_view_put/get are noun_phrase_verb, ewp_check_record reads as verb_noun, ewp_memory_context is noun_noun, and ewp_may_act is a modal phrase. The mixed conventions are readable but not predictable.
Seven tools is well within the ideal range and each one covers a distinct part of the evidence/warrant workflow without redundancy. Nothing feels bloated or too thin.
The surface covers the main lifecycle: persist and load EvidenceViews, append evidence and verification checks, evaluate warrants, gate actions, and retrieve context. It lacks list/update/delete operations, but the append-only record design and 'does not persist warrant' hint make these look intentional rather than critical gaps.