agent-gate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_GATE_LEDGER | No | Override the path to the ledger file. Default is ~/.agent-gate/receipts.jsonl | ~/.agent-gate/receipts.jsonl |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gate_checklistC | Return the checklist an agent must satisfy before it may claim a task done. |
| verify_gateB | Evaluate evidence against a gate. FAIL-CLOSED: a check is satisfied only if its value is exactly true; anything missing or non-true blocks. Returns {"passed": bool, "blocking": [check_ids]}. |
| record_receiptC | Append an honest, hash-chained receipt to the ledger and return it. verdict is typically one of: kept, killed, shipped, blocked. |
| read_receiptsA | Return every receipt plus whether the hash chain is intact (tamper-evident). |
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 4 tools
Each tool targets a distinct aspect of gatekeeping: checklist retrieval, receipt reading, receipt recording, and gate verification. No overlap in purpose.
Names mix patterns: 'gate_checklist' is a noun phrase, while 'read_receipts', 'record_receipt', and 'verify_gate' are verb_noun. The 'gate' prefix is used inconsistently.
Four tools is a reasonable number for a focused gatekeeping server, neither too few nor too many.
Core operations are covered, but missing tools to create or modify gates and checklists limits full lifecycle support.