Skip to main content
Glama

GATA Cafeteras

Recommend a coffee machine

recommend_coffee_machine
Read-onlyIdempotent

Recommends the type of coffee machine (bean-to-cup/superautomática, manual espresso with portafilter, capsule, drip, moka pot, French press, pour-over) for the user's habits, explains why, and returns example models with pressure, grinder, water tank, milk system, what to check, an Amazon.es buy_url (affiliate) and source URLs. No prices.

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

Input Schema

NameRequiredDescriptionDefault
needNoWhat the user wants, in their words (optional if the other fields are given).
drinkNoMostly: espresso (short/black or cortado), leche (with milk: cappuccino, latte), americano (long), variado (a bit of everything).
spaceNoCounter space: poco (little), normal, amplio (plenty).
effortNoboton = one button and done; ritual = enjoys grinding/tamping/pouring.
languageNoLanguage of the answer (default: es). Content is in Spanish; translate it if needed.
cost_per_cupNoHow much they want to spend per cup: minimo (as little as possible), medio, da-igual (doesn't matter).
cups_per_dayNoCoffees per day at home.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent lookup; the description adds genuinely useful behavioral context: what the answer contains (examples with pressure, grinder, tank, milk system, 'what to check', affiliate buy_url, source URLs) and the explicit negative constraint 'No prices', which prevents the agent from expecting pricing data.

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?

A single front-loaded sentence starting with the verb, listing output contents compactly. Dense but every clause carries information; slightly long for one sentence.

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?

There is no output schema, and the description does a fair job of describing the return payload. However, it never clarifies that all seven parameters are optional and that at least some input is needed for a meaningful recommendation, which is a real gap for an all-optional recommendation tool.

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 description coverage is 100% with five enums, so the schema carries the parameter burden. The description adds little beyond it — only the note that the answer is Spanish content to be translated, which is already stated on the language field.

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 and resource ('recommends the type of coffee machine') and enumerates the machine categories it can return, so an agent can tell this apart from brew_guide or capsule_compatibility 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 only implied — a pre-purchase recommendation based on user habits. There is no explicit when-to-use/when-not guidance and no routing to siblings such as cost_per_cup for running-cost questions or brew_guide for 'how do I use it' questions.

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