Skip to main content
Glama

getecoback-climate-weather

gebrauchtgeraet_angebot_sichtprobe_fotoausschnitt

Read-only

Bei verdeckten Fotobereichen festhalten, welche behaupteten Gebrauchsspuren ungeprüft bleiben — Prioritize a follow-up view of a claimed clear but obscured section.

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": {
      "zuordnung_belegt": "<zuordnung_belegt>",
      "pruefabschnitte": "<pruefabschnitte>",
      "nicht_gezeigt": "<nicht_gezeigt>",
      "ohne_spur_behauptet": "<ohne_spur_behauptet>",
      "spur_sichtbar": "<spur_sichtbar>"
    },
    "name": "gebrauchtgeraet_angebot_sichtprobe_fotoausschnitt"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicht_gezeigtYesDurch Zuschnitt oder Abdeckung nicht ausreichend dargestellte Abschnitte.
spur_sichtbarYesBei den tatsächlich sichtbaren Abschnitten auffällige Stellen.
pruefabschnitteYesEindeutig identifizierte Prüfabschnitte insgesamt.
zuordnung_belegtYesGehört das Bild nachweislich zum betrachteten Exemplar?
ohne_spur_behauptetYesDavon ausdrücklich als spurenfrei beworbene Abschnitte.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/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 little beyond the vague framing: it does not say whether a count, a classification, or a follow-up priority is produced, nor what happens when the visible and claimed sections conflict. 'Festhalten' (record) sits uneasily with the read-only annotation but is too ambiguous to call a contradiction.

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

Conciseness2/5

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

It is short, but the single sentence mixes German and English around an em dash, so it is not cleanly front-loaded and the key action is buried mid-sentence. Every clause is vague rather than wasteful, which is a specification problem rather than a length problem.

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?

With five required parameters, no output schema, and no nesting, the description should explain what decision or record the counts produce and how they combine. Instead it offers only a thematic gloss, leaving the agent unable to predict the result of a call.

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 all five required numeric/boolean parameters are documented in the schema, so the baseline is 3. The description gestures at the underlying concepts ('behaupteten Gebrauchsspuren ungeprüft', obscured vs. claimed-clear areas) but adds no concrete semantics linking them to specific fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a bilingual fragment ('Bei verdeckten Fotobereichen festhalten ... — Prioritize a follow-up view ...') that never states plainly what the tool computes or returns. 'Festhalten' hints at recording an assessment of obscured photo regions, but the verb+resource is never made explicit, and the opaque compound name supplies no help.

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 condition 'bei verdeckten Fotobereichen' and 'a claimed clear but obscured section' does imply the triggering situation: photos where a section asserted to be mark-free is cropped or covered. However, there is no explicit when-not guidance and no named alternative among the many sibling inspection tools, so the agent must infer the routing.

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