Skip to main content
Glama

getecoback-raumklima

vergleichstest_typischer_wert_quantilangabe

Read-only

Prüfe, welcher Aussageumfang hinter einem als typisch beworbenen Testwert steht — Verify the rank and coverage behind a reported typical test value

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": {
      "kennzahl": "<kennzahl>",
      "geordnete_beobachtungen": "<geordnete_beobachtungen>",
      "rang_unter_oder_gleich": "<rang_unter_oder_gleich>",
      "gleicher_auswertungsumfang": "<gleicher_auswertungsumfang>"
    },
    "name": "vergleichstest_typischer_wert_quantilangabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
kennzahlYesIn der Testmethodik ausdrücklich genannte Kennzahl
rang_unter_oder_gleichYesZahl der Beobachtungen unter oder gleich dem veröffentlichten Wert
geordnete_beobachtungenYesZahl vollständiger, passend abgegrenzter Beobachtungen
gleicher_auswertungsumfangYesBericht und Rangzählung verwenden nachweisbar dieselben Beobachtungen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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. Beyond that the description adds no behavioral context: it does not say what verdict is produced when 'gleicher_auswertungsumfang' is false, whether a mismatch blocks the result, or how the rank/coverage is reported. It essentially restates the tool name in two languages.

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?

The definition is short and front-loads the verb, with no filler sentences. The German/English duplication conveys the same content twice, which is mild redundancy rather than wasted explanation.

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 four required parameters are fully documented in the schema, so input-side completeness is fine. However, with no output schema and a check-style tool, the description never explains what the check yields or how an agent should act on a failed scope match, leaving the result side underspecified.

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, including the 'kennzahl' enum, are documented in the schema itself. The description adds no interpretation of what values or combinations mean, so the baseline of 3 is appropriate.

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 concrete verb ('Prüfe' / 'Verify') and a concrete object ('Aussageumfang / rank and coverage behind a reported typical test value'), so an agent knows this is a validation tool about quantile claims. It does not distinguish itself from nearby siblings such as 'vergleichstest_gewichtung_rangwechsel' or 'vergleichstest_gleiche_prueflinge_querwert', so it stays below 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 when-to-use guidance, no precondition (e.g. only when a value is advertised as 'typical'), and no named alternative for cases where the evaluation scope differs. The agent must infer the trigger situation entirely from the parameters.

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