Skip to main content
Glama

getecoback-climate-weather

kompaktspuel_als_zweitgeraet_altgang_tatsaechlich_entfallen

Read-only

Ermittelt ob ein Kompaktlauf einen bestehenden Maschinenlauf tatsächlich ersetzte oder nur gut passende Stücke verlagerte — Check whether using a compact second unit actually displaced an existing 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": {
      "bestand_ohne_kompakt": "<bestand_ohne_kompakt>",
      "bestand_mit_kompakt": "<bestand_mit_kompakt>",
      "kompakt_lauefe": "<kompakt_lauefe>",
      "gleiche_gesamtaufgabe": "<gleiche_gesamtaufgabe>"
    },
    "name": "kompaktspuel_als_zweitgeraet_altgang_tatsaechlich_entfallen"
  }
}

Input Schema

NameRequiredDescriptionDefault
kompakt_lauefeYesSeparat belegte Läufe des Kompaktgeräts.
bestand_mit_kompaktYesLäufe des bisherigen Geräts während der zweiten erprobten Ausführung.
bestand_ohne_kompaktYesVollständig beobachtete Läufe in der bisherigen Ausführung.
gleiche_gesamtaufgabeYesKein Pflichtstück fehlt und vollständige Bereitstellung im gleichen Zeitraum nachgewiesen?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description does not contradict it. The description adds genuine analytical context — that the tool discriminates displacement from mere load-shifting — but says nothing about how the four counts are combined, what evidence thresholds apply, or what form the verdict takes. Useful context, incomplete behaviour.

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 front-loaded sentence that states the discriminating question immediately, with the German original followed by an English rendering. Nothing is padded, though the bilingual duplication doubles the token cost for the same information.

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?

With no output schema, the description carries the burden of indicating what comes back, and it only implies a yes/no determination ('Ermittelt ob') without stating the return shape or how to read a negative result. For a read-only four-required-parameter comparison tool the input side is well covered by the schema, but the output side is left to inference.

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 each of the four parameters carries its own German description with min/max bounds, so the schema does the heavy lifting. The description's phrasing ('bestehenden Maschinenlauf', 'verlagerte Stücke') loosely maps to bestand_ohne_kompakt/bestand_mit_kompakt/kompakt_lauefe but adds no interpretation of gleiche_gesamtaufgabe or of how the counts should relate. Baseline 3 is appropriate.

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 uses a specific verb ('Ermittelt/Check whether') and a precise question: did a compact second unit actually displace an existing run, or merely shift well-fitting pieces. That is a clear, non-tautological purpose that an agent can distinguish from other kompaktspuel_* siblings by subject matter. It stops short of naming a sibling to contrast with, which keeps it at 4 rather than 5.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named despite a dense sibling set (kompaktspuel_bestandsgeraet_kauf_bis_eigenbeleg, kompaktspuel_vergleich_teilladung_gleichzahl_andere_gruppen, etc.). The usage is only inferable from the question the tool answers. That is thin routing for an agent choosing among many near-neighbours.

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