Skip to main content
Glama

Party food calculator

party_food_calculator
Read-onlyIdempotent

How much food and drink to buy for a party: appetizer pieces, then the mains, sides, salads, bread and desserts you pick, and drinks for the hours.

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": {
      "guests": "<guests>",
      "style": "<style>"
    },
    "name": "party_food_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
foodsNoDishes on the menu
hoursNoParty length, for drinks (default 3)
styleYes
drinksNo
guestsYesNumber of guests

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile needs no restating. Beyond that the description reveals almost nothing: it doesn't state the output shape (a shopping quantity list?), units, assumptions per guest, default behaviors when foods is omitted, or why hours is capped at 12. For a 5-parameter computation tool with no output schema, that leaves the agent guessing at results.

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

Conciseness4/5

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

One compact sentence with no filler, front-loaded with the core question. The awkward list ('appetizer pieces, then the mains, sides, salads, bread and desserts you pick, and drinks') is slightly convoluted but each phrase carries menu-scope information.

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

Completeness1/5

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

This is a multi-parameter calculation tool with 5 params, 60% schema coverage, no output schema, and a hidden enum of 34 dish values. The description should convey what gets returned (quantities per dish), units, and the style semantics; it conveys none of that.

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?

Schema coverage is 60%, and the description adds genuine meaning only for hours ('for drinks' - clarifying it feeds drink quantities, matching the schema's 'default 3'). It also signals the dietary categories via the food list, but adds nothing about style's three enum values, what omitting foods or drinks does, or how the maxItems caps matter. Baseline 3 given partial schema coverage.

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

Purpose3/5

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

The description implies a quantity estimator for party food and drink and enumerates categories (appetizers, mains, sides, salads, bread, desserts, drinks), but the verb is nominal: 'How much food and drink to buy' never states that the tool computes quantities from guests/style/hours. Siblings like turkey_calculator and ham_calculator are clearly per-dish calculators, so an agent can infer this is the whole-menu aggregate, but the description doesn't say that 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 when-to-use guidance and no routing to or away from siblings. It doesn't say whether this replaces per-item calculators like turkey_calculator or prime_rib_calculator, or how 'style' should be chosen. Usage is only implied by the description's menu framing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources