Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_vorfuehrung_eigene_last_untergrenze

Read-only

Eine gezeigte Gebrauchslast mit dem kleinsten eigenen Einsatz und dessen Zubehörzustand vergleichen — Check whether a demonstration actually covers the buyer’s minimum workload.

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": {
      "gleiche_aufgabe": "<gleiche_aufgabe>",
      "gezeigt_kg": "<gezeigt_kg>",
      "eigener_bedarf_kg": "<eigener_bedarf_kg>",
      "gezeigtes_ergebnis_geprueft": "<gezeigtes_ergebnis_geprueft>"
    },
    "name": "gebrauchtgeraet_vorfuehrung_eigene_last_untergrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
gezeigt_kgYesIn der Vorführung vor Start gewogene anrechenbare Last in kg.
gleiche_aufgabeYesSind Material, Programm und verwendete Teile für die beabsichtigte Aufgabe tatsächlich vergleichbar?
eigener_bedarf_kgYesKleinste relevante Last im eigenen Ablauf in kg.
gezeigtes_ergebnis_geprueftYesWurde das relevante Endergebnis des vorgeführten Laufs praktisch geprüft?

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 the safety profile is covered. The description adds that this is an adequacy judgment rather than a data lookup, but it does not say what kind of verdict is returned, how a failed 'gleiche_aufgabe' short-circuits the check, or what the unspecified 'Zubehörzustand' element means. The accessory-state clause introduces an element the inputs cannot supply.

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 a single sentence and front-loaded with the comparison. But the German and English halves are not equivalent — only the German half mentions 'Zubehörzustand' — so the bilingual pairing is redundant rather than reinforcing, and a reader cannot tell which version is authoritative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-required-parameter, read-only, closed-world check with full schema coverage and no output schema, the description conveys the core decision (demo load vs. own minimum plus verified result and task comparability). The residual gaps — verdict shape and the dangling accessory-condition reference — are minor at this complexity, though the latter is a real inconsistency worth removing.

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 all four parameters are already documented with units, ranges and intent, which sets the baseline at 3. The description adds no format, unit or dependency guidance beyond the schema, and its mention of accessory condition has no corresponding parameter, so it adds no usable parameter meaning.

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?

States a specific action: comparing a demonstrated usable load against the buyer's smallest own requirement and checking whether the demonstration covers that minimum. The verb+resource pair is identifiable. However, it claims to assess 'Zubehörzustand' (accessory condition) although no such input exists, and it does not distinguish itself from the near-identical sibling 'gebrauchtgeraet_testlast_eigener_ablauf_nur_kombination'.

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 'Check whether a demonstration actually covers the buyer's minimum workload' clause implies the evaluation context, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer the boundary against the many other 'Vorführung' siblings on its own.

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