Lemonade Stand 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 |
|---|---|
| start_gameB | Start a new lemonade stand game |
| buy_suppliesC | Purchase supplies for the lemonade stand |
| set_priceC | Set the price per cup of lemonade |
| sell_lemonadeD | Open for business and see today's results |
| next_dayC | Advance to the next day |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| start_lemonade_game | Start a new Lemonade Stand game with an introduction |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: buying supplies, advancing time, selling lemonade, setting price, and starting the game. An agent can easily distinguish between these core gameplay actions without confusion.
All tools follow a consistent verb_noun pattern (e.g., buy_supplies, set_price, start_game). The naming is uniform throughout, using snake_case and clear action-oriented verbs that align with the lemonade stand simulation domain.
With 5 tools, this is well-scoped for a lemonade stand game simulation. Each tool serves a specific, essential function (setup, resource management, time progression, sales, pricing), and there are no extraneous or missing tools for this domain.
The toolset covers the core lifecycle of a lemonade stand game: starting, buying supplies, setting price, selling, and advancing days. A minor gap is the lack of tools for viewing game state (e.g., checking inventory or finances), but agents can work around this by tracking results from sell_lemonade.