Skip to main content
Glama
La Marzocco MCP

La Marzocco MCP

by EmilbMadsen

get_firmware_status

Read-only

Check the firmware status of an espresso machine to see whether it is up to date or currently updating. Specify a serial number or use the configured machine.

Instructions

Firmware update status (whether the machine is up to date or updating).

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_firmware_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

B3.2/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 by structured data. The description adds genuine value by enumerating the possible status outcomes (up to date vs updating), which hints at a read-only polling use case, but says nothing about what happens when no machine is configured or how stale the status might be.

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 the purpose front-loaded and no filler. The parenthetical could arguably be a separate clause, but nothing is wasted.

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?

A one-parameter read-only tool with annotations, a fully documented schema, and an output schema carrying return values; the description needn't explain results. It is near-complete, with only the choice between this and get_machine_status left implicit.

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-machine fallback. The description adds no parameter meaning beyond that, which is the baseline case when the schema does all the work.

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 gives a specific verb+resource (firmware update status) and clarifies the two states it reports: up to date or updating. It is distinguishable from siblings such as get_machine_status or get_coffee_and_flush_counter by resource, though it never explicitly contrasts itself with the broader machine status tool.

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 the alternative get_machine_status, and no exclusions or prerequisites. The agent must infer from the tool name alone whether firmware state is included in machine status.

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