Skip to main content
Glama

getecoback-raumklima

auslands_datenblatt_de_angebot

Read-only

Technischen Auslandsbeleg vom deutschen Lieferumfang abgrenzen — Check how an overseas datasheet applies to a German offer.

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": {
      "modell_gleich": "<modell_gleich>",
      "markt": "<markt>",
      "deutsches_angebot_belegt": "<deutsches_angebot_belegt>"
    },
    "name": "auslands_datenblatt_de_angebot"
  }
}

Input Schema

NameRequiredDescriptionDefault
marktYesMarkt des Datenblatts.
modell_gleichYesExakte Variantenbezeichnung auf beiden Unterlagen gleich?
deutsches_angebot_belegtYesDokumentiert der Händler Stecker, Zubehör und liefernde Variante?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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 and the bar is lower. However, the description adds no behavioral context about the decision being made — no criteria for how the three inputs combine, no mention of what the result represents, and no note on whether the assessment is advisory or binding.

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?

Very short and front-loaded, which is good, but the German and English clauses are near-duplicates rather than complementary, and the English rendering drifts from the German meaning. It is compact but not maximally informative per sentence.

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?

There is no output schema, so the description bears the burden of explaining what is returned, yet it never says whether the result is a yes/no applicability verdict, a risk classification, or a list of discrepancies. For a three-required-parameter assessment tool whose whole value is the conclusion it draws, this is a significant omission.

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%, including a documented enum for 'markt', so the schema carries all parameter meaning. The description adds nothing beyond it, which is the expected baseline when the schema does the heavy lifting.

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 description names a resource ('Auslandsbeleg'/'overseas datasheet') and an action ('abgrenzen' / 'check how it applies'), so the domain is identifiable, but 'abgrenzen' is ambiguous about what the tool actually produces — a comparison, a verdict, or a classification of the German offer. The English gloss ('Check how an overseas datasheet applies') is not an exact equivalent of the German, leaving the operation partly vague.

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?

No statement of when this should be invoked versus other datasheet/offer-checking tools, and no prerequisites or exclusions. The agent is told the topic but not the triggering 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