Skip to main content
Glama

getecoback-climate-weather

miele_h7460_bp_betriebswert_genaues_datenblatt

Read-only

Den passenden Herstellerwert für einen unabhängig belegten Zustand des deutschen H 7460 BP auswählen — Read the correct power and transition fields for material number 11105690.

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": {
      "materialnummer": "<materialnummer>",
      "zustand": "<zustand>",
      "selbe_modell_und_marktvariante": "<selbe_modell_und_marktvariante>"
    },
    "name": "miele_h7460_bp_betriebswert_genaues_datenblatt"
  }
}

Input Schema

NameRequiredDescriptionDefault
zustandYesEindeutig dokumentierte Herstellerzeile.
materialnummerYesHerstellermaterialnummer der bestätigten deutschen Variante.
selbe_modell_und_marktvarianteYesEntsprechen Gerätekennung und Marktversion genau dieser deutschen Herstellerseite?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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=false, so the safety profile is covered. The description adds that the returned data comprises power and transition fields and that the material number is fixed, which is useful, but it says nothing about how selection resolves the ambiguous enum branches ('andere_nummer', 'offen') or what a failed match yields.

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 compact sentence split by a dash, with the purpose front-loaded and no filler. The German/English duplication is slightly wasteful and reads as two partially overlapping instructions rather than one, but it is far from verbose.

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?

With no output schema, three fully documented parameters, and read-only annotations, the description is adequate but thin. For a lookup whose whole difficulty is disambiguating states and variants, it should explain what 'power and transition fields' are and how unresolved inputs are handled.

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 two enums, so the parameter meanings are already documented in structured form. The description only restates the material number (11105690) and the documented-state precondition, adding nothing about the individual 'zustand' values or the boolean self-check.

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 concrete verb ('auswählen' / 'Read') and resource ('Herstellerwert', 'power and transition fields') for a specific product (German H 7460 BP, material number 11105690), so the operation is identifiable. It does not contrast itself with any of the many similarly named siblings, so an agent must infer the boundary from the name alone.

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?

The only qualifying condition is implicit in 'unabhängig belegten Zustand' — the state must already be independently documented. There is no explicit when-to-use/when-not statement, no pointer to an alternative for the undocumented or 'offen' cases, and no mention of what to do when model/market variant does not match.

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