gambit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APP_TRANSPORT | No | Set to 'streamable-http' to run the pre-production HTTP transport on localhost. It is not approved for remote production use. | stdio |
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 |
|---|---|
| gambit_check_contractA | Check compatibility with the walking-skeleton contract. Use this before relying on this pre-production server. It validates only the MCP adapter contract. It does not validate data, run Gambit, backtest, calculate risk, or provide investment advice. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| about | Return server identity, maturity, and non-trading safety boundary. |
| capabilities | Return implemented and explicitly unavailable capabilities. |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusing it with another. The description clearly states exactly what it validates and what it does not, leaving no ambiguity.
The name 'gambit_check_contract' follows a clear verb_noun pattern and is readable. However, with only one tool, there is no broader naming convention to assess, and the redundant 'gambit_' prefix is slightly awkward.
A single tool feels thin for a server, even one with a narrow scope. It is usable for its stated purpose but provides agents with a very limited surface.
The server's stated purpose is limited to checking contract compatibility for a pre-production adapter, and the tool fully covers that purpose. Missing capabilities like data validation or backtesting are explicitly out of scope, so they are not true gaps, but the surface is still minimal.