ConsumerSim MCP Proxy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONSUMERSIM_API_KEY | No | Optional API key for authentication. | |
| CONSUMERSIM_TIMES_PATH | No | Optional override for the times endpoint path. | |
| CONSUMERSIM_API_BASE_URL | Yes | The base URL of the private ConsumerSim backend API. | |
| CONSUMERSIM_FORECAST_PATH | No | Optional override for the forecast endpoint path. | |
| CONSUMERSIM_API_KEY_HEADER | No | Optional custom header name for the API key. | |
| CONSUMERSIM_API_KEY_SCHEME | No | Optional scheme for the API key (e.g., Bearer). | |
| CONSUMERSIM_SITE_DATA_PATH | No | Optional override for the site-data endpoint path. | |
| CONSUMERSIM_TIMEOUT_SECONDS | No | Optional timeout in seconds for backend requests. |
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 |
|---|---|
| forecast_lookupD | – |
| forecast_timesD | – |
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 2 tools
Both tools start with 'forecast_' and have no descriptions, making it impossible to distinguish their purposes. They likely overlap in functionality.
Both tools use consistent snake_case naming with the 'forecast_' prefix, following a clear pattern.
Only 2 tools for a server named 'ConsumerSim MCP Proxy' suggests an extremely narrow scope, likely insufficient for typical simulation tasks.
The server name implies simulation capabilities, but only forecast tools are present. Critical operations like simulation control or data retrieval are missing, making the surface severely incomplete.