Skip to main content
Glama

CostRail Food Cost Calculator

cost_dish_or_pour

Read-onlyIdempotent

Calculate plate cost, pour cost, food-cost percentage, and suggested menu price from natural language or structured ingredients.

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": {
      "text": "<text>"
    },
    "name": "cost_dish_or_pour"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesDish or pour description with pack prices and portion sizes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds only that inputs may be free-form natural language, but says nothing about underlying assumptions such as default target food-cost percentage, currency, or rounding.

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?

One sentence, front-loaded with the action verb and followed by the concrete outputs, with zero filler. Every clause contributes to identifying what the tool returns.

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 single-parameter, read-only calculation tool with no output schema, listing the four computed outputs is largely sufficient. Minor gaps remain around calculation assumptions (target food-cost percentage, currency, handling of missing portion data) that an agent might need when interpreting results.

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 100% for the single 'text' parameter, and its schema description already specifies 'pack prices and portion sizes'. The description's mention of 'natural language or structured ingredients' adds mild meaning about accepted formats but no syntax examples, so the baseline 3 applies.

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 ('Calculate') and enumerates exactly what is computed: plate cost, pour cost, food-cost percentage, and suggested menu price. It also names the accepted input forms (natural language or structured ingredients), so an agent knows precisely what the tool produces without opening the schema.

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?

Usage is implied by the enumeration of costing outputs, but there is no explicit guidance on when to prefer this over manual computation or what inputs are out of scope. With no sibling tools listed, alternatives are not a concern, yet no constraints or prerequisites are stated.

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.