mcp-gatehouse
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.
A demo order desk behind mcp-gatehouse. Reads run freely; add_note is logged; cancel_order needs a human's approval, asked in this client when it supports elicitation and on the server's terminal otherwise, and is denied if nobody approves within two minutes. Every call, allowed or denied, is written to an audit log.
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_ordersA | List every order on the desk as |
| lookup_orderA | Look up one order's customer, status and notes. Read-only; changes
nothing. Returns |
| add_noteA | Append a note to an order. Existing notes are kept — this never overwrites or cancels anything. Runs without approval, and every call is recorded in the audit log. To actually stop an order, use cancel_order. |
| cancel_orderA | Cancel an order. Irreversible, so it is gated: a human must approve before it runs, in this client's approval form if it shows one, else on the server's terminal. If they refuse, don't answer within two minutes, or there is nowhere to ask, the call is denied and the refusal is logged. To record information without cancelling, use add_note. |
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 has a clearly distinct action and target: list all orders, look up one order, append a note, or cancel an order. The descriptions explicitly cross-reference similar tools (e.g., add_note vs. cancel_order), removing ambiguity.
All four tools follow a consistent verb_noun snake_case pattern: list_orders, lookup_order, add_note, cancel_order. There is no mixing of conventions or vague standalone verbs.
Four tools is a well-scoped set for an order-desk workflow focused on reading, annotating, and cancellation. Each tool has a clear purpose and none appears redundant.
The surface covers listing, lookup, notes, and irreversible cancellation, but omits obvious order lifecycle operations such as creating orders or updating status/details. These gaps are workable for a narrow cancellation/note workflow but notable for general order management.