Skip to main content
Glama

getecoback-climate-weather

gebrauchtgeraet_testlast_eigener_ablauf_nur_kombination

Read-only

Zwei einzeln gezeigte Teilfunktionen von der benötigten Kombination im selben Arbeitsgang trennen — Verify whether a buyer-required joint use was actually demonstrated.

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": {
      "kombination_laut_anleitung": "<kombination_laut_anleitung>",
      "a_einzeln": "<a_einzeln>",
      "b_einzeln": "<b_einzeln>",
      "beide_ein_arbeitsgang": "<beide_ein_arbeitsgang>"
    },
    "name": "gebrauchtgeraet_testlast_eigener_ablauf_nur_kombination"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_einzelnYesWurde die erste Teilaufgabe einzeln mit Ergebnis gezeigt?
b_einzelnYesWurde die zweite Teilaufgabe einzeln mit Ergebnis gezeigt?
beide_ein_arbeitsgangYesWurden beide Teilaufgaben in demselben bestätigten Arbeitsgang mit geprüftem Ergebnis gezeigt?
kombination_laut_anleitungYesSind die gewünschte Kombination und die geplanten Teile für den gleichen Arbeitsgang freigegeben?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare this as a read-only, closed-world verification operation, and the description is consistent with that. It adds the concept of checking whether joint use was demonstrated, but it does not explain the return result or how the verification is resolved.

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?

The definition is short and contains no filler, with the key verification purpose stated in the English sentence. However, the bilingual phrasing and the cryptic German clause make it less cleanly structured than it could be.

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?

The tool has four required boolean parameters and no output schema, so the description should do more to explain what result is returned and how to interpret it. It covers the purpose adequately but leaves the verification outcome underspecified.

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 four boolean parameters are clearly documented in the schema. The description adds a conceptual link between individually shown functions and the required combination, but does not add parameter-level detail beyond what the schema already provides.

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 English phrase clearly states a specific verification purpose: "Verify whether a buyer-required joint use was actually demonstrated." It distinguishes individual demonstrations from the required combined use, but the German sentence is cryptic and no sibling tool is named.

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?

The description gives no explicit guidance on when to call this tool versus sibling verification tools, nor does it state exclusions or prerequisites. Usage is only implied by the buyer-required joint-use scenario.

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