Skip to main content
Glama

getecoback-climate-weather

induktion_magnet_am_boden_hersteller_widerspruch

Read-only

Werte die Magnetprobe am kalten Gefäßboden gemeinsam mit der exakten Herstellerkennzeichnung aus — Reconcile a cold base magnet observation and the exact cookware specification

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": {
      "hersteller_induktion": "<hersteller_induktion>",
      "magnet_probe": "<magnet_probe>",
      "quelle_zur_variante": "<quelle_zur_variante>"
    },
    "name": "induktion_magnet_am_boden_hersteller_widerspruch"
  }
}

Input Schema

NameRequiredDescriptionDefault
magnet_probeYesProtokollierte Beobachtung am kalten Gefäß
quelle_zur_varianteYesHerstellerdokument und vorhandenes oder angebotenes Gefäß anhand der exakten Kennung zugeordnet
hersteller_induktionYesExplizite Eignung für Induktion, bezogen auf genau die vorliegende Gefäßvariante

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 clear and the description does not contradict it. The description adds that two independent evidence strands (physical probe vs. manufacturer labeling) are assessed together, implying a reconciliation verdict, but it never says what happens when they disagree — the very case its name ('widerspruch') advertises. No return format or resolution policy is disclosed.

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, front-loaded sentence with no filler; the German and English renderings are duplicate content but serve as a bilingual gloss rather than padding. Nothing in it is wasted, though the em-dash bilingual format is slightly heavier than necessary.

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 three required parameters are fully specified and the tool is read-only, but there is no output schema, so the description should say what an 'Auswertung' yields — a contradiction verdict, a recommendation, or a confidence statement. For a reconciliation tool whose entire value is the resulting judgment, that gap leaves the agent guessing about the response.

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 fully documented, so the schema carries the parameter burden and baseline 3 applies. The description adds only the qualifier 'kalten Gefäßboden' (cold base) and 'exakte Herstellerkennzeichnung', which loosely map to magnet_probe and hersteller_induktion/quelle_zur_variante without adding new semantics such as how 'keine_probe' or 'offen' are treated in the evaluation.

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 ('Werte ... aus' / reconcile) and two concrete resources: the magnet probe at the cold vessel base and the exact manufacturer specification. An agent can distinguish it from siblings that probe only one evidence source (e.g. induktion_gefaessgriffe_kalte_aussenkontur_probe). It stops short of stating what the evaluation produces, which keeps it from a 5.

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 explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The pairing of a magnet observation with a manufacturer spec is implied by the wording, but the agent must infer it. With many induction-related siblings, at least a hint about which evidence combination selects this tool would be valuable.

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