lemonade-bench

by mxmarchal

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

lemonade_select_location

Select a named location to move your lemonade stand for the next day, from options like beach, park, or downtown.

Instructions

Move the lemonade stand to a named location for the next day.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "location": "<location>"
    },
    "name": "lemonade_select_location"
  }
}

Input Schema

Name	Required	Description	Default
`location`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.6/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description must carry the full burden of behavioral disclosure. It states the action and timing but does not mention potential side effects, costs, or any prerequisites, leaving the mutation behavior under-specified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no redundant words, effectively front-loading the action ('Move') and the temporal context ('for the next day').

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity tool with one enumerated parameter and no output schema, the description adequately covers the basic action and timing. It could be enhanced by referencing the location catalog or game effects, but it is not severely incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, but the single 'location' parameter is fully enumerated with clear, self-explanatory options. The description adds that the location is for the next day, but it does not elaborate on the meaning or consequences of different locations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Move' and clearly identifies the resource ('lemonade stand') and temporal scope ('for the next day'), making it easy to distinguish from other lemonade tools like buying supplies or setting prices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is used to change the stand's location for the upcoming day, but it does not explicitly state when to use it versus alternatives, nor does it reference the location catalog or other setup tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.