Skip to main content
Glama

getecoback-climate-weather

gebrauchtgeraet_sammlung_einzelfoto_oder_muster

Read-only

Bei einem Angebot mit mehreren Geräten Musterbilder und eindeutige Ansichten des ausgewählten Exemplars trennen — Check the evidence scope of a multi-unit listing.

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": {
      "sammelangebot": "<sammelangebot>",
      "identitaet_im_bild": "<identitaet_im_bild>",
      "detail_beim_exemplar": "<detail_beim_exemplar>",
      "austausch_vor_abholung": "<austausch_vor_abholung>"
    },
    "name": "gebrauchtgeraet_sammlung_einzelfoto_oder_muster"
  }
}

Input Schema

NameRequiredDescriptionDefault
sammelangebotYesUmfasst das Angebot mehr als ein Exemplar?
identitaet_im_bildYesIst das ausgewählte Exemplar auf der Übersichtsaufnahme eindeutig zugeordnet?
detail_beim_exemplarYesGehört die gezeigte Nahaufnahme eindeutig zu dieser Übersicht und demselben Exemplar?
austausch_vor_abholungYesDarf der Anbieter laut Abmachung ein anderes Exemplar bereitstellen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 safety is covered; the description adds only the narrow framing of multi-unit listings. It does not disclose what the agent gets back (a verdict, a flag, a recommended action), whether the four booleans are combined into a rule, or what happens when they conflict — the key behavioral question for a boolean-classifier tool.

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 plus a short English tagline — compact and front-loaded with no padding. The bilingual duplication is slightly redundant but costs little.

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?

For a four-required-boolean evaluation tool with no output schema, the description should explain what the booleans produce and how they are weighed. Instead it only names the topic, leaving the agent to guess the result format and the decision rule before committing four mandatory parameters.

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 each of the four booleans carries its own German question text, so the schema does the heavy lifting. The description's talk of Musterbilder vs. eindeutige Ansichten loosely echoes two parameters but adds no interpretation, thresholds, or combination logic beyond the schema.

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 identifies the subject area — separating sample/muster photos from unambiguous views of the chosen unit in a multi-unit listing — but never states the operation the tool performs (a verdict? a classification? a check?). The English gloss 'Check the evidence scope of a multi-unit listing' is a topic label, not a verb+resource statement, so an agent can guess the domain but not the action.

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 when-to-use or when-not-to-use guidance and no reference to any alternative. The sibling list contains closely related tools (e.g. gebrauchtgeraet_angebot_sichtprobe_fotoausschnitt), yet the definition gives no signal about which situation selects this one over those.

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