Skip to main content
Glama

getecoback-raumklima

backofenauszug_einzelansicht_belegt_ebene_oder_satz

Read-only

Ein Foto einer einzigen ausgestatteten Ebene vom Beleg des vollständigen angebotenen Satzes trennen — Separate verified rail positions from coverage implied by a photo caption.

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": {
      "auszug_mit_geraet_zugeordnet": "<auszug_mit_geraet_zugeordnet>",
      "erwartete_positionen": "<erwartete_positionen>",
      "beide_seiten_in_bild": "<beide_seiten_in_bild>",
      "nur_eine_seite_in_bild": "<nur_eine_seite_in_bild>",
      "sicher_fehlend": "<sicher_fehlend>"
    },
    "name": "backofenauszug_einzelansicht_belegt_ebene_oder_satz"
  }
}

Input Schema

NameRequiredDescriptionDefault
sicher_fehlendYesWeitere durch unabhängigen Beleg als fehlend bestätigte Positionen.
beide_seiten_in_bildYesDavon mit tatsächlich beidseitig sichtbarer Position.
erwartete_positionenYesFür dieses Angebot getrennt auf der Liste erwartete Positionen.
nur_eine_seite_in_bildYesWeitere jeweils nur einseitig sichtbare Positionen.
auszug_mit_geraet_zugeordnetYesSind alle Aufnahmen und das bestätigte Exemplar identisch zugeordnet?

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. The description adds only an abstract notion of separating single-level evidence from set-level evidence; it says nothing about how the five counts are combined, whether contradictions are flagged, or what the agent receives back. For a five-required-parameter adjudication tool this is thin added context.

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?

It is short and front-loads the German statement, but the bilingual duplication adds length without adding information, and the second half is a loose paraphrase rather than a clarification. Nothing is wasted in the sense of filler, yet the brevity comes at the cost of substance.

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?

The tool takes five required numeric/boolean inputs, has no output schema, and its name suggests a non-trivial evidence reconciliation. The description never explains the expected result nor how the counts relate, so an agent cannot tell what a correct invocation produces. For this complexity level the definition is under-specified.

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%, so every parameter (auszug_mit_geraet_zugeordnet, erwartete_positionen, beide_seiten_in_bild, nur_eine_seite_in_bild, sicher_fehlend) is already documented in the schema. The description adds no meaning about how these values interact or which are compared against which; baseline 3 applies.

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 does contain a specific verb ('trennen'/separate) and a resource split (a single equipped level's photo evidence vs. evidence for the whole offered set), so it is not a tautology. However, the German phrase and the English gloss are both abstract and neither states what the tool actually returns or does with the inputs, leaving the agent to guess whether it classifies, counts, or validates. Sibling names like backofenauszug_tatsaechlich_sichtbare_blechtiefe are equally cryptic, so no differentiation is achievable from the text.

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 guidance, no when-not-to-use, and no named alternative anywhere in the description. The phrase 'coverage implied by a photo caption' hints at a context but does not tell the agent which situation should route to this tool versus the many sibling backofenauszug tools.

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