Skip to main content
Glama

getecoback-climate-weather

gebrauchtgeraet_fehler_haeufigkeit_angabe_widerspruch

Read-only

Eine Aussage wie „selten“ gegen dokumentierte Einsatzanteile mit offenem Zeitraum prüfen — Detect an explicit intermittent-fault frequency mismatch from comparable records.

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": {
      "stoerung_gleich_erfasst": "<stoerung_gleich_erfasst>",
      "vollstaendig_gesehene_einsaetze": "<vollstaendig_gesehene_einsaetze>",
      "davon_stoerung": "<davon_stoerung>",
      "nicht_protokolliert": "<nicht_protokolliert>",
      "genannte_obergrenze_prozent": "<genannte_obergrenze_prozent>"
    },
    "name": "gebrauchtgeraet_fehler_haeufigkeit_angabe_widerspruch"
  }
}

Input Schema

NameRequiredDescriptionDefault
davon_stoerungYesDavon Einsätze mit der betrachteten Störung.
nicht_protokolliertYesWeitere bekannte Einsätze ohne verfügbares Ergebnis.
stoerung_gleich_erfasstYesBezeichnet das Protokoll genau dieselbe benannte Störung und denselben Zeitraum wie die Aussage?
genannte_obergrenze_prozentYesExplizit vom Anbieter genannte vergleichbare Prozentobergrenze.
vollstaendig_gesehene_einsaetzeYesVollständig protokollierte Einsätze mit bekannter Störung oder störungsfreiem Abschluss.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 useful framing that the comparison is against comparable records with an open/unbounded period, which affects interpretation. It does not disclose the verdict format or how unrecorded deployments (nicht_protokolliert) influence the outcome.

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?

A single compact sentence with the action front-loaded and the English gloss aiding disambiguation. No filler, though the dash construction slightly muddles emphasis.

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?

All five parameters are required and fully documented, so call mechanics are covered without an output schema. For a verdict-producing consistency check, though, the description never says what the result expresses or how edge cases (open period, undocumented deployments) are handled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all five parameters are self-documenting; the baseline is 3. The description contributes a little extra by framing the comparison as claim-vs-documented-share over an open period, which mirrors the scope parameter. No syntax or format details are added 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?

Names a specific operation (prüfen/detect a mismatch) against a specific resource (an explicit frequency claim like „selten“ vs. documented Einsatzanteile). The English gloss "Detect an explicit intermittent-fault frequency mismatch" makes the intended signal concrete. It could be sharper about what a positive/negative result means, but an agent can tell this is the frequency-claim consistency check rather than a document- or photo-check sibling.

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 scenario is implied by the phrasing (a seller-stated frequency claim being compared against records with an open period), so an agent can infer when it applies. However, there is no explicit when-to-use/when-not, no prerequisites, and no naming of alternative tools for related checks.

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