Skip to main content
Glama
La Marzocco MCP

La Marzocco MCP

by EmilbMadsen

get_coffee_and_flush_trend

Read-only

Retrieve daily coffee and flush counts for the last N days in your local timezone to track espresso machine usage trends across up to 30 days.

Instructions

Coffees and flushes per day for the last N days, in the user's local timezone.

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

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days, up to 30.
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.6/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 a meaningful behavioral detail the annotations do not: aggregation happens in the user's local timezone, which affects day-boundary bucketing. It omits anything about machine resolution fallback or empty-result behavior.

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?

A single front-loaded sentence with zero filler; the aggregation grain, time window, and timezone caveat all land immediately.

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 and full annotation coverage in place, the description only needs to carry the non-structured details, and it does cover the key one (local-timezone bucketing). It falls slightly short on how the machine is resolved when serial_number is omitted, despite the schema hinting at it.

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%, so both parameters (days, serial_number) are already fully documented in the schema, including the max of 30 and the list_machines provenance for serial numbers. The description echoes the N-days notion but adds no syntax or semantics beyond the schema; 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 states a specific resource and shape: coffees and flushes aggregated per day over the last N days, scoped to the user's local timezone. That distinguishes it adequately from sibling reads like get_coffee_and_flush_counter or get_last_coffees, though it never names an alternative explicitly.

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: 'last N days' signals a bounded trend query rather than a live counter, but there is no statement of when to prefer this over the counter or statistics siblings, and no prerequisites or exclusions are given.

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