Skip to main content
Glama
La Marzocco MCP

La Marzocco MCP

by EmilbMadsen

get_machine_settings

Read-only

Retrieve espresso machine settings—firmware versions, Wi-Fi signal, plumb-in status, and auto-update—using a serial number or the configured machine.

Instructions

Machine settings: firmware versions, wifi signal, plumb-in, auto-update.

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

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.6/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, so the safety profile is covered. The description adds no behavioral context beyond the field list — nothing about permissions, freshness/caching of settings, failure modes for an offline machine, or response shape, despite openWorldHint implying external variability. With an output schema present, return values needn't be explained, but the terse fragment leaves behavior essentially undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a seven-word fragment with no wasted words and the content list is front-loaded. However, brevity here comes at the cost of structure: there is no verb and no complete sentence, so it reads as a label rather than a definition. Short is good, but this is under-specification rather than disciplined concision.

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?

The structured data does much of the work: annotations cover the read-only/open-world profile, the schema fully documents the one parameter, and an output schema covers return values. What is missing is exactly the part only prose can supply — how this differs from get_machine_status and get_firmware_status, whose fields are echoed here. Adequate to invoke, insufficient to select confidently.

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 fallback to the configured or only machine. The description contributes nothing about the parameter, so the baseline of 3 applies. It neither adds nor detracts from what structured data provides.

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 is a noun phrase listing the resource's contents (firmware versions, wifi signal, plumb-in, auto-update), which tells an agent roughly what comes back but never states the action or scope. It does not distinguish itself from siblings like get_machine_status or get_firmware_status, both of which plausibly overlap with the named fields.

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 at all: no statement of what question this tool answers, no conditions for choosing it over get_machine_status or get_firmware_status, and no exclusions. The only routing hint available to the agent lives in the schema description of serial_number, not the tool description.

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