Skip to main content
Glama

getecoback-climate-weather

geraeteablage_saisonstart_teilzuordnung

Read-only

Gelagerte Saisonkomponenten zur nächsten Inbetriebnahme nach Herstellerablauf kontrollieren — Audit which stored set pieces still need checking before seasonal use.

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": {
      "modell_und_ablauf": "<modell_und_ablauf>",
      "am_geraet": "<am_geraet>",
      "in_box": "<in_box>",
      "pflege_offen": "<pflege_offen>",
      "soll": "<soll>"
    },
    "name": "geraeteablage_saisonstart_teilzuordnung"
  }
}

Input Schema

NameRequiredDescriptionDefault
sollYesVollständige Anzahl der dokumentierten Pflichtteile am Start.
in_boxYesWeitere geprüft zugeordnete Teile im Lagerkarton.
am_geraetYesBereits geprüft zugeordnete Teile des dokumentierten Satzes am Gerät.
pflege_offenYesWeitere vorhandene Satzteile, bei denen die vorgeschriebene Pflege oder Trocknung noch nicht bestätigt ist.
modell_und_ablaufYesSind die Lager- und Startvorgaben für das genaue Gerät geprüft?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful framing that this is a pre-season verification tied to a manufacturer schedule, but it says nothing about what gets compared or returned, leaving the actual behavior opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loaded, but the second sentence is essentially an English restatement of the German first sentence rather than new information, which is wasted space in a tool description of this length.

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 five required numeric parameters, a closed-world read-only audit, and no output schema, the description should explain the comparison logic and what a caller should expect back. It conveys the business context but leaves the mechanics of the audit unspecified, which is a clear gap for a five-parameter computation.

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 all five fields (soll, am_geraet, in_box, pflege_offen, modell_und_ablauf) are already documented in the schema. The description adds no further meaning about how these counts interact or which combinations are valid, so the baseline of 3 applies.

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 names an identifiable operation — auditing stored seasonal set pieces against the manufacturer's schedule before commissioning — with a concrete verb (kontrollieren/Audit) and resource (Gelagerte Saisonkomponenten). It does not, however, differentiate this tool from any sibling or state what the audit actually produces, so the agent knows the domain but not the exact output shape.

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 when-to-use or when-not-to-use guidance, no mention of alternatives, and no preconditions (e.g. that counts must be collected before calling). The phrase 'before seasonal use' implies timing but not a decision rule for selecting this tool over sibling audit 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