lemonade-bench

by mxmarchal

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

lemonade_get_staff_catalog

View the staff catalog with names, descriptions, daily costs, and hired status to make informed hiring decisions.

Instructions

Browse available staff as displayed: names, card descriptions, daily costs and hired state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lemonade_get_staff_catalog"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the burden. It discloses the content ('names, card descriptions, daily costs, hired state') and 'as displayed' adds context about the source, but it does not explicitly state that the tool is read-only or describe any potential side effects.

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?

A single sentence of 12 words, front-loaded with the verb 'Browse'. Every word contributes meaning, making it highly concise and well-structured.

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 zero-parameter catalog getter with no output schema, the description sufficiently covers what data is returned. It does not mention ordering or pagination, but these are unlikely to be relevant for a simple staff catalog.

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

Parameters4/5

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

The tool has zero parameters, so the description does not need to elaborate on them. The baseline score of 4 is appropriate for parameterless tools.

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 clearly states the resource ('staff') and the specific information it returns ('names, card descriptions, daily costs and hired state'). It distinguishes itself from sibling catalog tools by naming 'staff' explicitly.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus other catalog tools like lemonade_get_upgrade_catalog or lemonade_get_supply_catalog. The description only states the basic function without context or exclusions.

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