Skip to main content
Glama

getecoback-climate-weather

spuelprognose_balken_symbol_zwei_notizen_register

Read-only

Zwei Vorabbalken nur zuordnen, wenn Energie- oder Wassersymbol und Auswahlbedingungen belegbar sind — Audit the labels on qualitative forecast notes.

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_symbol": "<a_symbol>",
      "b_symbol": "<b_symbol>",
      "gleiche_auswahl_und_beladung": "<gleiche_auswahl_und_beladung>",
      "beide_vor_start": "<beide_vor_start>"
    },
    "name": "spuelprognose_balken_symbol_zwei_notizen_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_symbolYesAbgelesenes Symbol bei Notiz A.
b_symbolYesAbgelesenes Symbol bei Notiz B.
beide_vor_startYesBeide Notizen stammen von der Vorhersage vor dem Start.
gleiche_auswahl_und_beladungYesProgramm, Extras, Beladung und übliche Bedingungen sind in beiden Notizen gleich belegt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the domain precondition (symbol + selection conditions must be 'belegbar'), which is useful behavioral context. It does not say what happens when the condition fails — refusal, empty result, or a diagnostic — which is the key behavioral question for an audit 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?

One compact sentence with the constraint front-loaded and no filler. The bilingual em-dash splice between German and English hurts readability slightly but costs no length.

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?

Four required parameters with full schema coverage and read-only annotations mean the basics are covered, but with no output schema and no title, the description should explain the return shape and the failure mode. It states the gating rule yet leaves the result of the audit undocumented, which is a real gap for a tool whose whole purpose is producing an audit verdict.

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% and all four parameters carry German descriptions, so the schema does the heavy lifting. The description's mention of 'Energie- oder Wassersymbol' and 'Auswahlbedingungen' loosely maps to a_symbol/b_symbol and gleiche_auswahl_und_beladung, but adds no semantics beyond the schema — notably nothing about the 'unbekannt' enum value or how 'beide_vor_start' interacts with the assignment rule.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The English clause 'Audit the labels on qualitative forecast notes' supplies a verb and a resource, but the German preamble ('Zwei Vorabbalken nur zuordnen ...') describes a conditional assignment rule rather than what the tool actually returns. An agent cannot tell from this whether the tool audits, assigns, or registers — the name says 'register' while the description says 'audit'. No sibling differentiation is offered.

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?

There is an explicit entry condition: use only when an energy or water symbol and the selection conditions are demonstrable. However, no when-not branch, no prerequisites about the notes pre-dating the start, and no alternative tool is named for the case where the symbols are not verifiable. Guidance is present but partial.

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