Skip to main content
Glama

getecoback-climate-weather

q350_tr_dokumentauswahl_artikelnummer_revision

Read-only

Ordnet die deutsche V0126-Quellzeile nur der nachgewiesenen Q350-TR-Artikelnummer zu — Validate the documented market and exact Q350 TR article before quoting the revision.

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": {
      "artikel": "<artikel>",
      "unterlage": "<unterlage>",
      "markt_de": "<markt_de>"
    },
    "name": "q350_tr_dokumentauswahl_artikelnummer_revision"
  }
}

Input Schema

NameRequiredDescriptionDefault
artikelYesArtikelnummer außen am Gerät oder im exakten Angebot.
markt_deYesZuordnung zur deutschen Ausführung belegt?
unterlageYesProtokollierter Quellenstand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 safety profile is covered and the bar is lower. The description adds one useful behavioral constraint — assignment happens 'nur der nachgewiesenen' article, i.e. it refuses to infer — but says nothing about what happens on an unproven or unavailable source, or what the tool produces.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded, with the substantive German clause first. However, the English portion is not a translation but a separate injunction, so the two halves do not reinforce each other and the reader must reconcile them.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A read-only validation tool with three fully-documented enum parameters and no output schema. Because no output schema exists, the description should explain what a call yields (a verdict, a mapping, a rejection) and it does not, leaving the agent unable to anticipate the result of a mismatch or an 'offen' input.

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% with enum values and per-parameter descriptions in German, so the schema carries the parameter meaning. The description adds the concept that only a 'nachgewiesene' article qualifies, which slightly sharpens how the 'offen'/'andere' enum members should be treated, but it does not address the markt_de flag or unterlage semantics beyond what the schema states.

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 German clause names a specific action (assigning the German V0126 source line to a verified Q350 TR article number) and the domain nouns (V0126, Q350-TR) do distinguish it from generic siblings. But the English half is an imperative instruction ('Validate ... before quoting the revision') rather than a statement of what the tool does or returns, so an agent cannot be fully certain whether this performs a validation, a lookup, or a recording step.

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?

'before quoting the revision' gives an implied ordering constraint, which is real guidance. There is no when-not condition, no statement of what to do when the article is 'offen' or 'andere', and no named alternative tool among the many q350_tr_* siblings.

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