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.
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 |
|---|---|
| lookup_orderB | Look up an order's status. |
| add_noteC | Attach a note to an order. (The api_key never reaches the log.) |
| cancel_orderA | Cancel an order. Requires approval — the gate fails closed. |
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 3 tools
Each tool has a clearly distinct purpose: looking up status, adding a note, and canceling an order. No overlap.
All three tools follow a consistent verb_noun pattern in snake_case (lookup_order, add_note, cancel_order).
Three tools is well-scoped for an order management server, covering essential operations without unnecessary bloat.
Covers core order operations (read, update via note, delete via cancel), but missing an update_order or list_orders tool, which are minor gaps.