Skip to main content
Glama

getecoback-climate-weather

vergleichstest_teilnoten_spannweite_luecke

Read-only

Grenze einen gewichteten Vergleich ein, wenn eine Teilnote fehlt — Bound a weighted test comparison when one component score is missing

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": {
      "note_belegt": "<note_belegt>",
      "gewicht_belegt": "<gewicht_belegt>",
      "volle_andere_note": "<volle_andere_note>",
      "skala_und_gewichte_belegt": "<skala_und_gewichte_belegt>"
    },
    "name": "vergleichstest_teilnoten_spannweite_luecke"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_belegtYesVorliegende Teilnote auf der vereinbarten Skala 0 bis 100
gewicht_belegtYesGewicht der vorliegenden Teilnote in Prozent
volle_andere_noteYesGesamtnote des Vergleichsgeräts für dieselben beiden Kriterien
skala_und_gewichte_belegtYesBeide Teilnoten sind auf 0 bis 100 begrenzt; Kriterien, Gewichtung und Modellabgleich bestätigt

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 agent knows this is a closed, side-effect-free computation. The description adds the missing-input framing, which is real context. It does not disclose what the bound actually is (interval endpoints, whether it is tight, what assumptions the bound rests on), which is the behavior that matters most for a computation whose result drives a decision.

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 sentences with the trigger condition front-loaded, no filler and no repetition of the tool name. The German/English duplication adds length but serves a bilingual audience rather than padding the content.

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?

There is no output schema, so the description is the only place the return value could be characterized, and it is silent on what bounding means in practice. For a four-required-parameter computation used in a comparison workflow, the agent is left to guess the shape of the result. The safety profile and input contract are adequately covered; the output contract is not.

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 all four parameters carry their own descriptions, so the schema carries the burden and a baseline of 3 applies. The description does implicitly map 'eine Teilnote fehlt' onto note_belegt versus volle_andere_note, but adds no units, ranges, or weighting-normalization details beyond the schema.

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 verb+resource are specific: it bounds a weighted comparison when one component score is missing, which is a distinctly narrower scope than a plain weighted-score tool. The bilingual restatement reinforces rather than obscures the purpose. It stops short of 5 because it never names or distinguishes itself from the nearby comparison-test siblings such as vergleichstest_gewichtung_rangwechsel.

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?

The description does give one concrete trigger — use it when a Teilnote is missing — which is genuine when-to-use guidance. However, it never states what to use instead when all scores are present, nor any prerequisites, so the agent must infer the complement from sibling names alone.

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