Skip to main content
Glama

getecoback-raumklima

gebraucht_rolle_arbeitsbreite_ausgebrochene_abschnitte

Read-only

Sichtbare Lücken entlang einer zugänglichen Reinigungsrolle als überlappende Längenbereiche dokumentieren — Record distinct visibly affected spans along a roller without projecting cleaning performance.

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": {
      "zugang_laut_anleitung": "<zugang_laut_anleitung>",
      "breite": "<breite>",
      "a_von": "<a_von>",
      "a_bis": "<a_bis>",
      "b_von": "<b_von>",
      "b_bis": "<b_bis>"
    },
    "name": "gebraucht_rolle_arbeitsbreite_ausgebrochene_abschnitte"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_bisYesEndmarke der ersten Auffälligkeit.
a_vonYesStartmarke der ersten sichtbaren Auffälligkeit in mm.
b_bisYesEndmarke der zweiten Auffälligkeit.
b_vonYesStartmarke der zweiten sichtbaren Auffälligkeit in mm.
breiteYesGemessene Arbeitsbreite in mm.
zugang_laut_anleitungYesIst die äußere Sichtprüfung an der ausgebaut vorliegenden Rolle ohne weiteren Eingriff zulässig?

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 covered. The description adds a real scope limit ('without projecting cleaning performance') and an access precondition, but says nothing about how overlapping or duplicate spans are treated or what the tool returns. 'Dokumentieren' also hints at record creation, which sits in mild tension with the read-only annotation without rising to a contradiction.

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?

It is a single front-loaded sentence, which is good, but the German and English halves largely restate each other, effectively doubling length without adding information. Jargon such as 'ausgebrochene Abschnitte' and 'Projektion der Reinigungsleistung' is dense relative to the one actionable constraint it conveys.

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

Completeness4/5

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

There are six required numeric/boolean parameters with full schema descriptions, no output schema, and annotations covering read-only behavior, so the description need not do much more. The remaining gap is small: nothing is said about validity constraints between the two spans or what a successful call produces.

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 parameter carries an explicit mm-based description, so the baseline is 3. The description contributes only the notion of 'überlappende Längenbereiche', which hints that a_von/a_bis and b_von/b_bis form two spans but never states ordering or non-overlap rules.

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 a concrete verb and object: documenting visible gaps along an accessible cleaning roller as overlapping length spans. The closing clause ('without projecting cleaning performance') bounds the purpose further. It does not, however, distinguish this from the many sibling tools that also deal with 'Abschnitte', leaving the specific-vs-sibling test partly unmet.

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?

Usage is only implied: the roller is 'zugänglich' and the task is documentation, not performance projection, which suggests when it is appropriate. There is no explicit statement of when not to use it, no pointer to an alternative sibling, and no stated prerequisite beyond what the required 'zugang_laut_anleitung' flag already encodes.

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