Skip to main content
Glama

getecoback-raumklima

vergleichstest_gleiche_prueflinge_querwert

Read-only

Prüfe, wie viele physische Prüfgeräte beide Teile eines kombinierten Testversprechens belegen — Count units with both parts of a combined performance claim

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": {
      "geraete_gesamt": "<geraete_gesamt>",
      "leistung_belegt": "<leistung_belegt>",
      "verbrauch_belegt": "<verbrauch_belegt>",
      "beide_je_geraet": "<beide_je_geraet>",
      "identitaet_nachvollziehbar": "<identitaet_nachvollziehbar>"
    },
    "name": "vergleichstest_gleiche_prueflinge_querwert"
  }
}

Input Schema

NameRequiredDescriptionDefault
geraete_gesamtYesUnterschiedliche physische Geräte desselben Modells im betrachteten Bericht
beide_je_geraetYesDavon Geräte, für die beide Messungen in passenden Betriebsbedingungen zugeordnet sind
leistung_belegtYesDavon Geräte mit beobachteter Leistungsmessung
verbrauch_belegtYesDavon Geräte mit klar zugeordneter Verbrauchsmessung
identitaet_nachvollziehbarYesPrüflingseinheiten und Messbedingungen beider Tabellen sind abgleichbar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish that this is a safe, closed-world read. The description adds the subject of the count—physical devices satisfying both parts of a combined claim—but says nothing about return shape, consistency requirements, or edge cases. With annotations carrying the safety profile, this is a modest 3.

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 a single front-loaded statement plus an English rendering, with no padding. The bilingual repetition is mildly redundant but does not obscure the core purpose. It is compact and readable, meriting a 4.

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?

This is a computation-style tool with five required numeric/boolean inputs and no output schema, so the description should ideally clarify the return value and how the counts relate. It implies a count but leaves the output shape and consistency conditions implicit; the fully described schema mitigates but does not eliminate the gap. A 3 is appropriate.

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 all five parameters are documented in the input schema. The description does not add syntax, constraints, or relationships among the counts beyond what the schema says, so the baseline 3 applies.

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 gives a specific verb ('Prüfe'/'Count') and a precise object ('physische Prüfgeräte, die beide Teile eines kombinierten Testversprechens belegen'), which is enough to distinguish this from other comparison-test tools. It does not explicitly name a sibling or contrast its scope, so it stops short of 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 or when-not-to-use guidance, and no alternative tool is named. The purpose implies a context, but an agent gets no explicit routing help; this matches the 2 anchor for a description that provides no usage guidance.

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