Skip to main content
Glama

getecoback-climate-weather

datenblatt_korrektur_widerspruch

Read-only

Zwei widersprüchliche Zahlen nach Modell, Prüfpunkt und ausdrücklicher Korrektur einordnen — Reconcile two numeric specifications using scope and explicit corrections.

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": {
      "a": "<a>",
      "b": "<b>",
      "zeile_gleich": "<zeile_gleich>",
      "korrektur": "<korrektur>"
    },
    "name": "datenblatt_korrektur_widerspruch"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesErster Zahlenwert in bereits vereinheitlichter Einheit.
bYesZweiter Zahlenwert in derselben Einheit.
korrekturYesWelche Zahl ersetzt laut ausdrücklicher Notiz die andere für diese Zeile?
zeile_gleichYesIdentisches Modell, dieselbe Messgröße und gleicher Prüfpunkt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 and the description adds that reconciliation is driven by scope plus an explicit correction note. What remains undisclosed is the outcome: since there is no output schema, the agent cannot tell whether the tool returns a chosen value, a verdict, or a prose justification. That is a meaningful behavioral gap for a decision tool.

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 that leads with the concrete situation (two contradictory numbers) before the mechanism. The German/English duplication roughly doubles the length without adding information, which keeps it just short of a 5, but nothing is padded or vague.

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?

For a four-required-parameter, closed-world, read-only computation with full schema coverage, the description covers the input side adequately. Because there is no output schema, the description should say what the reconciliation produces, and it does not — that is the one substantive omission an agent would notice at call time.

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 coverage is 100% and each of the four parameters carries its own German description and enum/range constraints, so the baseline is 3. The description's mention of 'Modell, Prüfpunkt und ausdrücklicher Korrektur' loosely maps to zeile_gleich and korrektur but adds no semantics beyond what those schema descriptions already spell out.

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 states a specific operation on a specific resource: reconcile two conflicting numeric specifications, scoped by model, checkpoint and an explicit correction note. The bilingual restatement makes the intent unambiguous even though the opaque German tool name alone would not. It does not, however, contrast itself with any sibling, so an agent must infer from domain alone that this is the conflict-resolution helper rather than a datasheet reader.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phrase 'zwei widersprüchliche Zahlen' — call it when two numbers for the same line disagree — but there is no explicit when-to-use statement, no precondition (e.g. units already normalized), and no named alternative for the case where the numbers do not conflict. The agent must derive the trigger condition itself.

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