Skip to main content
Glama
La Marzocco MCP

La Marzocco MCP

by EmilbMadsen

get_last_coffees

Read-only

Retrieve recent espresso shots from your La Marzocco machine, newest first, with extraction time, dose mode, target temperature, and validity. Set a limit to control how many shots return.

Instructions

The machine's most recent shots, newest first (La Marzocco keeps the latest 15).

Each shot has its end time, extractionSeconds, dose mode, target temperature and whether La Marzocco considers it valid. extractionSeconds is pump time measured by the machine, not a scale timer, so it is usually a few seconds shorter than a scale shows.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many shots to return.
serial_numberNoMachine serial number from list_machines. Leave empty to use the configured machine, or the only machine on the account.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, so the safety profile is already covered; the description adds real value beyond that by disclosing the server-side retention cap of 15 shots and explaining that extractionSeconds is machine pump time rather than a scale reading. It stops short of describing pagination or empty-state behavior, but the domain caveat about the timer is exactly the kind of context annotations cannot convey.

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?

Three short sentences, front-loaded with the resource and ordering, followed by scope and one high-value measurement caveat. Nothing repeats the schema or title, and every sentence carries information.

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

Completeness5/5

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

An output schema exists, so return values need no further explanation, yet the description still clarifies the meaning of extractionSeconds for the caller. For a two-parameter read-only tool with full schema coverage and annotations, nothing an agent needs in order to call it correctly is missing.

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% and both parameters are documented inline, so the schema does the heavy lifting. The note that La Marzocco keeps the latest 15 gives the limit maximum a reason, but that is marginal added meaning over the schema's own max of 15.

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 resource and scope: the machine's most recent shots, newest first, capped at the latest 15. An agent can distinguish this from aggregate siblings like get_statistics or get_coffee_and_flush_trend without opening any 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 'most recent shots' framing, but there is no explicit when-to-use or when-not guidance and no named alternative for aggregate or historical queries. The agent must infer that trend/statistics tools cover longer-horizon questions.

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