Skip to main content
Glama
La Marzocco MCP

La Marzocco MCP

by EmilbMadsen

get_machine_status

Read-only

Retrieves current espresso machine status, including power state, coffee and steam boiler states and targets, pre-brewing, and back flush settings.

Instructions

Current machine status: on or standby, coffee and steam boiler state and targets, pre-brewing, and back flush. From the dashboard in La Marzocco's app.

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_machine_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by stating the data comes 'from the dashboard in La Marzocco's app,' hinting at the source and possible staleness, but it never states freshness expectations or refresh behavior, which matters for a 'current status' read.

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 short sentences with the payload contents front-loaded and no filler. The trailing 'From the dashboard in La Marzocco's app' is slightly tangential but short enough to earn its place as source context.

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?

With an output schema present, return values need not be explained, and the one optional parameter is fully covered by the schema. The description supplies enough for an agent to call it correctly, with only freshness/latency left unspecified.

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% and the single optional serial_number parameter is fully documented in the schema, including the default-to-configured-machine behavior. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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

Purpose4/5

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

The description names a specific resource and enumerates exactly what status is returned: power state (on or standby), coffee and steam boiler state and targets, pre-brewing, and back flush. This clearly separates it from sibling reads like get_machine_settings or get_statistics, though it never names those siblings as alternatives.

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: the word 'Current' signals a live-state read as opposed to the historical data siblings (get_statistics, get_last_coffees) provide. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool.

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