Skip to main content
Glama

GATA Cafeteras

Cost per cup

cost_per_cup
Read-onlyIdempotent

Computes the cost per cup, per month and per year with the prices the USER gives: capsules (pack price and capsules per pack) and/or beans or ground coffee (pack price, pack grams and grams per cup), plus optional milk cost per cup. It only uses the prices passed in the arguments; with no prices it returns an error listing what is missing.

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": "cost_per_cup"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer (default: es). Content is in Spanish; translate it if needed.
cups_per_dayNoCups per day (default 1).
grams_per_cupNoGrams of coffee per cup (default 8; espresso 7-9 g, double 14-18 g).
beans_pack_gramsNoGrams in that pack (e.g. 1000).
beans_pack_priceNoPrice of the bean or ground coffee pack in euros, as given by the user.
capsules_per_packNoCapsules in that pack.
milk_cost_per_cupNoOptional cost of the milk per cup in euros.
capsule_pack_priceNoPrice of the capsule pack in euros, as given by the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for the extra context it adds: it performs no price lookup and depends entirely on argument values, and it fails fast with a diagnostic listing missing inputs. Return shape is only loosely implied ('per month and per year'), which keeps this from a 5.

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?

Two sentences, front-loaded with the verb and the computed outputs before the input detail. The nested parenthetical enumeration is dense but every clause carries information; there is no filler or repetition.

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 an 8-parameter, zero-required, schema-rich calculator with no output schema, the description covers inputs, the error path, and the computed outputs. It leaves the defaults (cups_per_day, grams_per_cup) and the language behavior to the schema, which documents them adequately, so nothing critical is missing.

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?

Schema coverage is 100%, so baseline is 3, but the description goes further by grouping the flat schema properties into meaningful bundles: capsule_pack_price pairs with capsules_per_pack, while beans_pack_price pairs with beans_pack_grams and grams_per_cup. That combination logic is not expressed anywhere in the schema and is genuinely useful for correct invocation.

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?

States a specific verb (computes) and a specific resource set (cost per cup, per month, per year), and enumerates the two input modes (capsules vs. beans/ground). An agent can identify this as a coffee-cost calculator without opening the schema, and it is clearly distinct from siblings like brew_guide or capsule_compatibility.

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

Usage Guidelines4/5

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

The description establishes the key precondition — it only works with prices the user supplies — and states that calling it with no prices yields an error listing what is missing. It does not name alternative tools or explicitly say when to prefer it, but for a self-contained calculator the usage context is clear enough.

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