Skip to main content
Glama

getecoback-climate-weather

folgemodell_messwert_uebernahme

Read-only

Prüfen, wie ein Messwert beim Wechsel zu einer neuen Modellgeneration bezeichnet werden darf — Separate unchanged specifications from measured performance of a successor.

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": {
      "gen": "<gen>",
      "vergleichspunkt": "<vergleichspunkt>",
      "hersteller_uebernahme": "<hersteller_uebernahme>"
    },
    "name": "folgemodell_messwert_uebernahme"
  }
}

Input Schema

NameRequiredDescriptionDefault
genYesBezug des ursprünglichen Messprotokolls.
vergleichspunktYesBetriebsart und Messbedingungen dokumentiert?
hersteller_uebernahmeYesÜbernahme genau dieser Spezifikation auf die neue Variante schriftlich dokumentiert?

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 need only add behavior. It adds that this is an eligibility/admissibility determination rather than a data fetch, which is useful. It does not disclose what the determination returns (e.g., allowed vs. must-rename verdict) or what rule drives it, and there is no output schema to fill that gap.

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?

Two short clauses with the purpose front-loaded and no padding. The German and English halves partially restate each other, which is mildly redundant, but the total length is appropriate for the complexity.

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 three-parameter, fully documented, read-only decision tool with no output schema, the definition is adequate but thin. The decision logic itself (what combination of the three inputs permits keeping the measurement label) is never described, which is the main thing an agent would need to trust the result.

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%, so the three parameters and the enum are already documented, making 3 the baseline. The description's distinction between 'unchanged specifications' and 'measured performance of a successor' loosely frames the hersteller_uebernahme and vergleichspunkt flags, but adds no interpretation of how the enum value genaue_neue_variante/vorgaenger/unbekannt changes the outcome.

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 action (Prüfen/prüfen, ob eine Bezeichnung zulässig ist) and a specific object (Messwert bei Wechsel zu einer neuen Modellgeneration), and the second clause sharpens the intent to separating unchanged specifications from successor-measured performance. An agent can tell roughly what decision the tool makes. It does not, however, distinguish itself from similarly scoped siblings such as energielabel_messwert_abgleichen.

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 only implied: the tool is for cases where a measurement is carried over to a successor model generation. There is no explicit statement of when to call it versus when not to, and no alternative sibling is named as the fallback for adjacent comparison tasks.

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