Trading Simulator MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileC | Get your team's profile information |
| update_profileC | Update your team's profile information |
| get_balancesB | Get token balances for your team |
| get_portfolioC | Get portfolio information for your team |
| get_tradesC | Get trade history for your team |
| get_priceC | Get the current price for a token |
| get_token_infoC | Get detailed information about a token |
| get_price_historyC | Get historical price data for a token |
| execute_tradeC | Execute a trade between tokens |
| get_quoteC | Get a quote for a potential trade |
| get_competition_statusC | Get the status of the current competition |
| get_leaderboardC | Get the competition leaderboard |
| get_competition_rulesB | Get the rules and configuration details for the competition |
| get_healthB | Basic health check for the trading simulator API |
| get_detailed_healthB | Detailed health check with information about all services |
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 15 tools
Most tools have distinct purposes, but there is some potential confusion between get_health and get_detailed_health, as both relate to health checks. Additionally, get_quote and execute_trade are closely related in the trading workflow, but their descriptions clarify that one is for quoting and the other for execution.
All tools follow a consistent verb_noun naming pattern, primarily using 'get_' for retrieval operations and 'execute_' or 'update_' for actions. This uniformity makes the tool set predictable and easy to navigate for an agent.
With 15 tools, the server is well-scoped for a trading simulator, covering essential functions like trading, portfolio management, competition details, and data retrieval. Each tool appears to serve a specific purpose without redundancy.
The tool set covers core trading operations (e.g., execute_trade, get_quote, get_balances) and competition features (e.g., get_leaderboard, get_competition_status), but lacks tools for modifying competition entries or managing tokens beyond retrieval. Minor gaps exist, but agents can likely work around them.