analysis-gym
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANALYSIS_GYM_DB_PATH | No | Path to store the database file. Defaults to 'analysis_gym.sqlite3' in the working directory. | analysis_gym.sqlite3 |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| record_predictionA | Record one immutable pre-earnings forecast. expected_earnings_at must be an ISO 8601 timestamp with a timezone. Revenue, EBITDA, net profit, and free cash flow must use the same reporting currency. post_earnings_close is the expected first regular-session close after release. |
| record_actualsB | Record published actuals and settle earlier predictions for the event. EBITDA is operating income plus depreciation and amortization. Free cash flow is operating cash flow minus capital expenditure. For a pre-market release, use that session's close; for an after-hours release, use the next regular session's close. |
| get_resultsA | Return predictions, per-metric errors, and the configuration leaderboard. Lower symmetric mean absolute percentage error (SMAPE) is better. Set settled_only=false to include predictions whose actuals are not recorded yet. |
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 clear, distinct purpose: recording predictions, recording actuals, and fetching results. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (get_results, record_actuals, record_prediction), making them predictable and easy to understand.
With 3 tools, the server is tightly scoped to the core operations of the earnings analysis domain—recording predictions, recording actuals, and retrieving results. No unnecessary tools.
The tool surface covers the full lifecycle of the domain: creating predictions, recording actuals to settle them, and retrieving results with performance metrics. No obvious gaps.