Skip to main content
Glama
La Marzocco MCP

La Marzocco MCP

by EmilbMadsen

get_coffee_and_flush_counter

Read-only

Retrieve the total number of coffees and flushes an espresso machine has made, optionally for a specific serial number, to track usage.

Instructions

Total number of coffees and flushes the machine has made.

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

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

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds no behavioral context beyond the purpose sentence: it does not explain scope, authentication needs, rate limits, or how the total is computed, though it does not contradict the annotations.

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?

The description is a single front-loaded sentence with no redundant wording. It is terse but appropriately sized for a simple counter tool.

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 a simple read-only counter, the annotations, complete schema coverage, and output schema carry most of the needed context. The description omits usage guidance and sibling differentiation, but those gaps are not critical to invoking the tool correctly.

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?

The single serial_number parameter has 100% schema description coverage, including its optional default and fallback behavior. The description adds no parameter meaning beyond the schema, so the baseline score of 3 is appropriate.

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 states a specific resource and metric: total coffees and flushes the machine has made. It clearly indicates a counter-retrieval operation, but it does not distinguish this total from siblings such as get_coffee_and_flush_trend or get_statistics.

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 exclusions, and no mention of alternatives such as the trend or statistics tools. The agent must infer the appropriate context from the tool name and sibling names alone.

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