Skip to main content
Glama
La Marzocco MCP

La Marzocco MCP

by EmilbMadsen

get_statistics

Read-only

Retrieve La Marzocco machine statistics including recent coffees and total coffee and flush counters. Reads the stats widgets selected in the app for the configured or specified machine.

Instructions

The statistics widgets selected in La Marzocco's app, e.g. the last coffees and the total coffee and flush counters.

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

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

C2.9/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 safety is covered. The description does add one genuinely useful behavioral fact: the returned set is user-configured 'widgets selected in the app', so results vary per account. It says nothing about latency, pagination, or failure modes when no widgets are configured.

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 short sentence with no padding. It is front-loaded with the core concept, though the 'e.g.' list of widget examples consumes the back half and creates ambiguity rather than clarity.

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?

An output schema exists, so return values need not be explained, and annotations cover the read-only profile. However, the description never states what the tool does as an action, nor how it relates to the closely-named sibling tools, leaving a real selection ambiguity for an otherwise simple single-parameter 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 coverage is 100% and the single serial_number parameter is fully documented in the schema, including the default behavior of using the configured machine. The description adds nothing 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.

Purpose3/5

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

The description identifies the resource as 'the statistics widgets selected in La Marzocco's app' but is a bare noun phrase with no verb, so it never states that it retrieves/fetches them. The examples given ('last coffees', 'total coffee and flush counters') overlap with sibling tools like get_last_coffees and get_coffee_and_flush_counter without explaining how this tool differs from them.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when not to use it, and no reference to the sibling tools whose names appear in the description's examples. An agent must guess whether to call this or get_last_coffees / get_coffee_and_flush_counter.

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