Skip to main content
Glama
La Marzocco MCP

La Marzocco MCP

by EmilbMadsen

get_schedule

Read-only

Retrieves a La Marzocco espresso machine's smart standby, wake-up/sleep schedules, and early start settings so you can review current automation before adjusting it.

Instructions

Smart standby, wake-up/sleep schedules and early start settings.

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

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 safety is covered; the description adds no behavioral context whatsoever beyond naming settings categories. It says nothing about whether an empty/default machine resolution is used, whether schedules can be absent, or any freshness/caching behavior — all left to the schema and output schema.

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?

It is short with no wasted words, but it is an unstructured fragment with no leading verb or object, so it is under-specified rather than genuinely concise. Nothing is front-loaded because there is no sentence structure to front-load.

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 tool is a simple read with one optional, fully documented parameter and an output schema, so the description's burden is low and it is arguably sufficient to identify the tool. Still, it omits any linkage to sibling read tools and any statement of what schedule concepts it actually returns.

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?

With a single optional parameter at 100% schema description coverage, the schema already explains the serial_number fallback chain fully. The description adds no meaning beyond the schema, 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 is a noun-phrase fragment listing content domains (standby, wake/sleep schedules, early start) rather than a verb+resource statement; the verb is only implied by the tool name. An agent can infer it returns schedule-related settings, but nothing distinguishes it from the sibling get_machine_settings, which plausibly overlaps.

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 reference to alternatives such as get_machine_settings or get_machine_status. The only routing hint in the whole definition ('serial number from list_machines') lives in the schema, not the description.

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