Skip to main content
Glama

getecoback-climate-weather

fritz_302_router_firmware_mindeststand

Read-only

Prüfe die angegebenen DECT- und Firmwarevoraussetzungen für den FRITZ!Smart Thermo 302 — Check the documented DECT and firmware requirements for Thermo 302

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "router": "<router>",
      "dect_basis": "<dect_basis>",
      "firmware_hauptversion": "<firmware_hauptversion>",
      "firmware_nebenversion": "<firmware_nebenversion>"
    },
    "name": "fritz_302_router_firmware_mindeststand"
  }
}

Input Schema

NameRequiredDescriptionDefault
routerYesTypbezeichnung der vorhandenen Box
dect_basisYesVorhandene integrierte DECT-Basis der Box
firmware_hauptversionYesErste Zahl von FRITZ!OS, beispielsweise 6 bei 6.83
firmware_nebenversionYesZweite Zahl von FRITZ!OS, beispielsweise 83 bei 6.83

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only that the requirements are 'documented', but does not explain what the check produces, how 'offen' or 'anderes_fritz_modell' are handled, or whether a mismatch results in an error or a verdict.

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?

The definition is a single front-loaded sentence with no filler, and the bilingual German/English phrasing is efficient. It could be marginally tighter, but nothing is wasted.

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?

All four required parameters are documented via the schema, and the read-only annotation covers the safety profile. However, with no output schema, the description should say what the tool returns (a verdict, a matched requirement list, or an error) and it does not, leaving a meaningful gap for interpreting results.

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%, with enum values and numeric bounds documented, so the parameters are already well specified. The description only generically refers to 'angegebenen DECT- und Firmwarevoraussetzungen' and adds no syntax or interpretation guidance beyond the schema.

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 names a specific verb ('Prüfe' / 'Check') and a concrete resource (DECT and firmware requirements for the FRITZ!Smart Thermo 302), so an agent can tell what the tool is for. It does not explicitly differentiate itself from any sibling, but the device-specific scope makes accidental selection unlikely.

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 guidance on when to call this tool versus alternatives, no prerequisites, and no exclusions. The agent is left to infer from the name and description alone that this is a compatibility pre-check.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources