Skip to main content
Glama

getecoback-climate-weather

gebrauchtgeraet_vorfuehrung_stoppursache_qualifiziert

Read-only

Das beobachtete Programmende von Abbruch und unbekanntem Ende getrennt notieren — Distinguish a completed demonstration from a seller-stopped or unobserved run.

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": {
      "eindeutig_gleicher_lauf": "<eindeutig_gleicher_lauf>",
      "ende": "<ende>",
      "ergebnis_geprueft": "<ergebnis_geprueft>"
    },
    "name": "gebrauchtgeraet_vorfuehrung_stoppursache_qualifiziert"
  }
}

Input Schema

NameRequiredDescriptionDefault
endeYesBeobachteter Zustand bei Ende der Aufzeichnung.
ergebnis_geprueftYesIst das für den Käufer relevante Ergebnis am Ende tatsächlich geprüft?
eindeutig_gleicher_laufYesGehören Beginn, Ablauf und gegebene Endmeldung zum selben vorgeführten Programm?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the description's added value is in explaining what kind of distinction the tool makes. It identifies the relevant ending categories (completed, seller-stopped, unobserved) beyond what the annotations provide, though it does not explain the return format.

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 compact and front-loads the purpose before the English gloss. The bilingual duplication is slightly redundant but still clear and appropriately sized.

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 simple read-only qualification tool with fully described parameters and safety annotations, the description is adequate for understanding the core task. However, it omits usage guidance and does not describe what result the agent should expect, which is more noticeable because there is no output schema.

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 input schema already documents all three parameters and the enum values. The description reinforces the separation between abort and unknown endings but adds no syntax or field-level meaning beyond the schema.

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 states a specific action: record the observed program ending and distinguish a completed demonstration from a seller-stopped or unobserved run. It clearly names the classification task, though it does not differentiate this tool from similarly named sibling qualification tools.

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 when-to-use guidance, no exclusions, and no named alternatives. The intended context is inferable from the phrase 'beobachtete Programmende', but an agent must guess when this tool is preferable to the many sibling 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