Skip to main content
Glama

getecoback-raumklima

kompaktspuel_ladeprobe_passt_und_spruehraum_getrennt

Read-only

Hält Einlegen, freies Schließen und getrennten dokumentierten Sprühraum als eigene Ladebefunde fest — Separate loading, closure and documented spray clearance.

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": {
      "eingesetzt": "<eingesetzt>",
      "schluss": "<schluss>",
      "spruehraum": "<spruehraum>"
    },
    "name": "kompaktspuel_ladeprobe_passt_und_spruehraum_getrennt"
  }
}

Input Schema

NameRequiredDescriptionDefault
schlussYesBelegter normaler Schließzustand ohne Kraft.
eingesetztYesGemeldeter Einlegebefund der konkreten Gruppe.
spruehraumYesBeleg zur Anordnung nach Anleitung, ohne laufende Maschine zu beobachten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds little beyond the schema and leaves "hält ... fest" ambiguous – with readOnlyHint=true it is unclear whether findings are persisted or only validated, and no output behavior is disclosed. That ambiguity is exactly the kind of context the description should resolve.

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?

One short sentence is appropriately front-loaded, but it is immediately duplicated in English as a literal gloss, which adds no information an agent lacks. The bilingual repetition is filler rather than clarification.

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 three fully described required enums and readOnlyHint given, the inputs are sufficiently covered. The gap is the missing output description – there is no output schema, so the agent cannot tell whether it receives a verdict or an echo, which matters given the "passt" framing in the name.

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 enum carries its own explanatory text, so the baseline of 3 applies. The description merely lists the same three fields in prose without adding format, precedence, or edge-case meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a concrete verb ("festhalten") and the three resources it captures (Einlegen, freies Schließen, getrennter Sprühraum), so the domain is recognizable. However, it only restates the three required parameters and never says whether the tool evaluates them (the name says "passt") or merely echoes them, and nothing distinguishes it from the many other kompaktspuel_* siblings.

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 guidance on when to use this tool rather than a sibling, no prerequisites, and no statement about when-not to use it. The agent must infer from the name alone that this is the separate-recording variant versus the combined ones.

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