Skip to main content
Glama
Sign In
lemonade-bench

lemonade-bench

by mxmarchal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

lemonade_set_staff

Hire or fire one staff member to adjust staffing for upcoming business days.

Instructions

Hire or fire one staff member for subsequent days.

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": {
      "staff": "<staff>",
      "hired": "<hired>"
    },
    "name": "lemonade_set_staff"
  }
}

Input Schema

NameRequiredDescriptionDefault
hiredYes
staffYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must disclose side effects. It identifies the mutation (hire/fire) and timing, but does not mention consequences such as costs, availability limits, irreversibility, or how the change affects current/future day scenarios.

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?

Single concise sentence, front-loaded with the action, no filler. All content is relevant.

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

Completeness3/5

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

For a simple two-parameter setter, the description covers the core action and timing, but with no annotations or output schema it leaves out operational constraints and return behavior. It is minimally adequate but not rich.

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 phrase 'hire or fire' clarifies that the boolean 'hired' maps to the action, and 'one staff member' corresponds to the staff parameter. However, with 0% schema description coverage, it does not add much beyond the schema and leaves the enum values unexplained.

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?

Clearly states the action (hire or fire) and the resource (one staff member) and the temporal scope (subsequent days), distinguishing it from read-only sibling tools like lemonade_get_staff_catalog.

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?

Provides no guidance about when to use this tool versus alternatives, such as consulting lemonade_get_staff_catalog before hiring or firing. It only implies the change applies to future days, but no explicit when/when-not or prerequisite is given.

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

Deploy Server

Other Tools