Skip to main content
Glama

getecoback-climate-weather

kompaktspuel_kaufentscheidung_pilot_mit_abbruchgrenze

Read-only

Hält eine bewusst beendete Ladeprobe als Reichweitenbeleg fest, ohne eine nicht ausgeführte Reinigung mitzuzählen — Preserve the observed loading limit of an intentionally stopped trial.

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": {
      "grund": "<grund>",
      "letzter_bestaetigter_satz": "<letzter_bestaetigter_satz>",
      "benoetigte_gruppen": "<benoetigte_gruppen>",
      "maschinenlauf_belegt": "<maschinenlauf_belegt>"
    },
    "name": "kompaktspuel_kaufentscheidung_pilot_mit_abbruchgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
grundYesDokumentierter Ausgang der Ladeprobe.
benoetigte_gruppenYesFür diesen Einsatz notwendige Gruppen.
maschinenlauf_belegtYesFür die erforderliche volle Ladung liegt ein abgeschlossener Nutzungsnachweis vor.
letzter_bestaetigter_satzYesAnzahl kompletter eigener Gruppen mit überprüfter Vorbereitung.

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 supplied externally. The description adds a useful behavioral rule: do not count a cleaning that was not actually performed. It does not describe return values, persistence semantics, or any limitations beyond that counting rule.

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 front-loads the core action before the exclusion. The German sentence and English translation repeat the same content, which is slightly redundant, but the overall wording remains compact and readable.

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 four-parameter, read-only tool with full schema coverage, the description supplies the key semantic caveat about not counting unperformed cleaning. It still lacks guidance for selecting this tool among numerous similar kompaktspuel siblings and does not clarify output behavior. It is adequate but not complete.

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 required parameters have descriptions in the schema. The description does not add parameter-specific meaning beyond the schema, so the 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 states a specific action and object: preserving the observed loading limit of an intentionally stopped trial. It also adds the exclusion that an unperformed cleaning must not be counted. It does not differentiate the tool from the many similar kompaktspuel siblings, so it falls short of a 5.

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 phrase 'bewusst beendete Ladeprobe' implies the tool is used when a loading trial was intentionally stopped, and the exclusion clarifies what should not be counted. However, there is no explicit when-to-use versus alternatives guidance and no named sibling. The usage context is therefore inferable but not fully directed.

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