Skip to main content
Glama

getecoback-raumklima

geraet_testzitat_einordnen

Read-only

Prüfen, wie eng ein Testsieger-Zitat formuliert werden muss — Qualify a best-in-test claim by model, test group and date.

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": {
      "quelle": "<quelle>",
      "exakt": "<exakt>",
      "testfeld": "<testfeld>"
    },
    "name": "geraet_testzitat_einordnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
exaktYesStimmt die geprüfte Variante vollständig mit dem Angebot überein?
quelleYesArt des Belegs.
testfeldYesSind Vergleichsgruppe und Testzeitpunkt angegeben?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered and the description need not restate them. It adds that the assessment hinges on model, test group and date, but says nothing about what the evaluation returns (e.g. a verdict or required wording), which matters since no output schema exists.

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?

A single front-loaded sentence with the core task stated first. The German and English halves are partially redundant, which costs a little space but aids comprehension rather than obscuring it.

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 assessment tool this is close to sufficient, but with no output schema the description should say what the qualification result looks like. As written, an agent knows the inputs' purpose but not the shape or decision criteria of the response.

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%, so all three parameters (quelle, exakt, testfeld) are already documented in the schema, establishing the baseline of 3. The description's mention of 'model, test group and date' loosely maps onto testfeld but adds nothing for quelle's evidence-type enum or for exakt's full-match condition, and 'model' is not a parameter at all.

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 task: judging how narrowly a 'Testsieger' (best-in-test) claim must be phrased, qualified by model, test group and date. That is concrete enough to distinguish it from sibling tools like geraet_wahl or angebot_lagerstatus_zitieren. It stops short of a crisp verb+resource framing because the bilingual phrasing makes the object slightly abstract.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named for overlapping quote-qualification or offer-comparison tasks. The context is only implied by the word 'Testsieger-Zitat', leaving the agent to infer the trigger condition.

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