Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_bedienmarken_lesbarkeit_bedarfsweg

Read-only

Lesbare Anzeigen und Symbole mit der konkret vorgesehenen Bedienung verknüpfen — Check whether a worn control label affects the intended local workflow.

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": {
      "ablauf_belegt": "<ablauf_belegt>",
      "pflicht_marken": "<pflicht_marken>",
      "vor_ort_lesbar": "<vor_ort_lesbar>",
      "belegte_externe_hilfe": "<belegte_externe_hilfe>"
    },
    "name": "gebrauchtgeraet_bedienmarken_lesbarkeit_bedarfsweg"
  }
}

Input Schema

NameRequiredDescriptionDefault
ablauf_belegtYesSind benötigte Bedienpunkte und Anzeige im eigenen geplanten Ablauf anhand der Anleitung identifiziert?
pflicht_markenYesFür den geplanten Ablauf benötigte einzelne Bedien- oder Ablesepunkte.
vor_ort_lesbarYesDavon am vorgesehenen Standort direkt lesbar.
belegte_externe_hilfeYesVon den übrigen Punkten mit separat bestätigter dauerhaft verfügbarer Ablese- oder Orientierungshilfe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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, but the description adds little behavioral context beyond that. With no output schema, the description should say what the tool produces from the four counts (e.g., a ratio of readable-to-required marks, a verdict threshold) and it does not, nor does it mention any prerequisite that external help must be separately confirmed.

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 with no filler, but it is bilingual duplication (German and English say the same thing) and the front-loaded German clause is the more opaque of the two. The clearer statement of intent arrives second rather than first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a four-required-parameter assessment tool with no output schema, so the description must carry the burden of explaining what the computed result means and how the counts combine. It conveys the domain question but not the outcome or its interpretation, which is a substantial gap for a tool an agent cannot inspect post-call.

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 each of the four parameters is already documented in the schema; the description adds only the framing that marks are 'worn' and belong to an intended workflow. It gives no hint about how pflicht_marken, vor_ort_lesbar and belegte_externe_hilfe relate to one another in the calculation, so 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 English clause states a concrete assessment task: check whether a worn control label affects the intended local workflow, which pairs readable displays/symbols with the actually planned operation. The resource is identifiable, though the leading German clause is a nominalized abstraction that is harder to parse. No named sibling is contrasted, so differentiation from items like oberflaechenspur_in_funktionszone or test_reihenfolge_nutzermodus_wiederfinden is left to inference.

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, no prerequisites, and no reference to alternatives among the many sibling tools about device condition and test workflows. At best the purpose sentence implies the situation ('intended local workflow'), leaving the agent to guess the trigger condition.

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