Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_originalkarton_aufgedruckt_enthalten

Read-only

Zubehörbilder auf einem mitgegebenen Karton von tatsächlich bestätigten Einzelteilen trennen — Avoid counting printed pack contents as received components.

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": {
      "karton_zuordnung_geprueft": "<karton_zuordnung_geprueft>",
      "karton_zeigt": "<karton_zeigt>",
      "durchgesehen": "<durchgesehen>",
      "davon_gefunden": "<davon_gefunden>"
    },
    "name": "gebrauchtgeraet_originalkarton_aufgedruckt_enthalten"
  }
}

Input Schema

NameRequiredDescriptionDefault
durchgesehenYesDavon bei geprüfter Öffnung überprüfte Positionen.
karton_zeigtYesFür den eigenen Zweck relevante, auf dem Karton abgebildete Zubehörpositionen.
davon_gefundenYesDavon im Paket überprüft vorhandene, passende einzelne Positionen.
karton_zuordnung_geprueftYesGehört der Karton nachweislich zur angebotenen Variante?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 an agent knows this is a closed-world, non-mutating evaluation. The description adds genuine value by naming the failure mode it guards against (mistaking printed box contents for delivered parts). It does not say what the tool returns, how the counts are combined, or what happens when `karton_zuordnung_geprueft` is false.

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?

Two short clauses with no filler, and the core operation is front-loaded before the caveat. The mixed German/English phrasing is slightly awkward but each half contributes distinct content rather than repeating itself.

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?

For a four-parameter, all-required derivation tool with no output schema, the description explains the intent but not the result: an agent cannot tell whether it returns a corrected part count, a flag, or the inputs echoed with a judgement. Given the rich schema and read-only annotations, the remaining gap is moderate rather than severe.

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 the four parameters, including the boolean ownership check, are documented in the schema itself. The description only loosely touches the ownership concept ('mitgegebenen Karton') and adds no interpretation of the numeric fields, so the schema does the heavy lifting and the baseline of 3 applies.

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 concrete operation on a concrete artifact: separating accessory depictions printed on a supplied box from actually confirmed individual parts. That is specific enough that an agent can tell it is not the same as the other `gebrauchtgeraet_*` inspection tools. It stops short of 5 because the verb 'trennen' does not say what the tool actually produces (a derived count, a verdict, a difference).

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 clause 'Avoid counting printed pack contents as received components' implies the situation this tool is for: verifying a used device whose original packaging shows accessory images. However, no explicit when-to-use condition, prerequisite, or named alternative sibling is given, so the guidance is implied rather than stated.

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