Skip to main content
Glama

getecoback-raumklima

backofenzubehoer_nachkauf_bestand_eigenes_exemplar

Read-only

Bei Angeboten für ein bestimmtes Schienenpaar einen ausdrücklichen Teilebeleg von bloßem Zustands- oder Shopbestand trennen — Check whether claimed seller stock is tied to a complete identified unit.

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": {
      "passung_unabhaengig": "<passung_unabhaengig>",
      "anbieterstatus": "<anbieterstatus>",
      "aktuelles_exemplar": "<aktuelles_exemplar>",
      "anderer_ersatz_ausreichend": "<anderer_ersatz_ausreichend>"
    },
    "name": "backofenzubehoer_nachkauf_bestand_eigenes_exemplar"
  }
}

Input Schema

NameRequiredDescriptionDefault
anbieterstatusYesVorliegender Verkäuferstatus.
aktuelles_exemplarYesGehört die vorhandene Prüfung genau zum tatsächlich bereitgestellten Exemplar?
passung_unabhaengigYesExakte Herstellerzuordnung zum eigenen Gerät.
anderer_ersatz_ausreichendYesDeckt vorhandenes, passend bestätigtes Zubehör den gewünschten Handgriff bereits ab?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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. The description adds the decision rule the tool encodes (documented part evidence vs. list/shop status), but says nothing about what happens with the inputs or what kind of result comes back; for a read-only evaluation tool that is an acceptable but not generous level of disclosure.

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 triggering context front-loaded, so there is little waste. The German-then-English restatement is duplicative but arguably aids interpretation of the dense terminology rather than padding.

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?

Four required, fully documented enum parameters and clean read-only annotations cover the input side. With no output schema, though, the description should say what the evaluation yields (a verdict, a flag, a classification) — that is left entirely unstated, which is the main completeness gap for a decision tool.

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% and three of four parameters carry enums with their own descriptions, so the schema does the semantic work. The description's framing of 'Teilebeleg' versus 'Zustands- oder Shopbestand' loosely echoes the anbieterstatus values but adds no field-level meaning 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 description names an action (separate an explicit parts record from mere condition/shop stock) and a subject (offers for a specific rail pair), plus an English gloss narrowing it to 'is claimed seller stock tied to a complete identified unit'. That is more than a restated name, but the phrasing is abstract jargon and gives no hint of how it differs from near-neighbours such as angebot_lagerstatus_zitieren or the other backofenzubehoer_* rules.

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?

'Bei Angeboten für ein bestimmtes Schienenpaar' provides a situational trigger for use, which is better than none. However, there is no explicit when-not, no prerequisite, and no named alternative for the adjacent stock-citation decision, so the agent must infer the boundary itself.

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