Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_oberflaechenspur_in_funktionszone

Read-only

Sichtbare Spuren in berührten Funktionszonen vor dem Kauf separat begutachten lassen — Distinguish wear on a working interface from nearby cosmetic marks.

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": {
      "bereiche_belegt": "<bereiche_belegt>",
      "an_funktionsflaeche": "<an_funktionsflaeche>",
      "daneben": "<daneben>",
      "lage_offen": "<lage_offen>",
      "betrieb_unauffaellig_behauptet": "<betrieb_unauffaellig_behauptet>"
    },
    "name": "gebrauchtgeraet_oberflaechenspur_in_funktionszone"
  }
}

Input Schema

NameRequiredDescriptionDefault
danebenYesSeparat beobachtete Spuren daneben.
lage_offenYesWeitere Spuren mit noch ungeklärter Lage.
bereiche_belegtYesIst anhand der vorgesehenen Arbeitsweise bekannt, wo Teile tatsächlich anliegen oder sich bewegen?
an_funktionsflaecheYesSichtbare Spuren im Kontakt- oder Bewegungsbereich.
betrieb_unauffaellig_behauptetYesHat der Anbieter lediglich störungsfreien Betrieb behauptet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 agent knows this is a safe, closed-world evaluation. The description adds the conceptual separating rule (functional-zone wear vs. nearby marks), which is real behavioral context. It says nothing about what the caller receives back, how the five required inputs combine into a conclusion, or what happens when evidence is ambiguous.

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 sentence with the distinguishing rule front-loaded and no filler. The German half is somewhat compressed and the English half does the clarifying work, so the pairing reads as slightly redundant rather than wasteful.

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?

Five required parameters, no output schema, and only a minimal readOnly annotation mean the description must carry a lot, yet it explains only the core axis of the decision. An agent can tell what topic it is assessing but not what a completed call yields or how conflicting inputs (e.g. claimed flawless operation alongside observed traces) are resolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines all five parameters and the baseline is 3. The description goes beyond that by articulating the operational distinction that governs how evidence is split between 'an_funktionsflaeche' and 'daneben' — the exact boundary an agent would otherwise have to guess at. It does not cover the boolean evidence-quality flags, but the added meaning is genuine.

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 subject (visible traces in touched functional zones) and a specific distinction the tool makes: wear on a working interface versus nearby cosmetic marks. That is more than a restatement of the name. It does not, however, say what the tool actually produces (a verdict, an assessment, a categorized report), so an agent knows the topic but not the output form.

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?

The phrase 'vor dem Kauf separat begutachten lassen' implies the context of use (pre-purchase, get the area assessed on its own) rather than stating it as guidance. There is no explicit when-not-to-use condition and no named alternative among the many sibling tools that deal with used-device evidence. Usage is inferable but not spelled out.

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