Skip to main content
Glama

getecoback-raumklima

pflegeetikett_foto_zeichenrand_und_balken

Read-only

Auf einem abgeschnittenen Etikettfoto prüfen, ob der Bereich für Unterstriche sichtbar ist und welche Information offenbleibt — Distinguish readable centers from cropped treatment bars.

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": {
      "bereich": "<bereich>",
      "mitte_lesbar": "<mitte_lesbar>",
      "rand_unten": "<rand_unten>"
    },
    "name": "pflegeetikett_foto_zeichenrand_und_balken"
  }
}

Input Schema

NameRequiredDescriptionDefault
bereichYesNur Waschbottich oder professioneller Kreis.
rand_untenYesBereich mit möglichen Balken unterhalb des Zeichens.
mitte_lesbarYesSind Zahl oder Buchstabe und eine mögliche Durchstreichung klar lesbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 agent knows this is a safe, closed-world inspection with no side effects. The description adds the behavioral framing that the tool tolerates cropped inputs and reports remaining uncertainty, but says nothing about the form of the verdict, confidence handling, or what happens when mitte_lesbar is true but the bar is cut off.

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 description is short and front-loaded, which is good, but it effectively states the same discrimination twice — once in German and again in an English gloss that adds no new information. The bilingual duplication spends words without extending meaning.

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?

Three required parameters are fully specified and the operation is read-only, so the essentials are covered. With no output schema, the description should indicate what kind of result comes back (a verdict plus the listing of missing information), which it only gestures at with 'welche Information offenbleibt'.

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% with two enums fully documented, so the schema carries the parameter burden and a 3 is the baseline. The description's mention of 'Bereich für Unterstriche' and 'Balken' loosely ties to rand_unten and adds a little conceptual grounding, but no semantics beyond the schema.

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 German sentence names a specific verb ('prüfen') and a specific resource ('abgeschnittenen Etikettfoto'), plus the exact judgment being made: whether the underscore area is visible and what information remains. The English tail ('Distinguish readable centers from cropped treatment bars') reinforces the discrimination task. It is a narrow, well-identified check, though the two clauses overlap rather than cleanly delimiting scope.

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 implied by the constraint 'auf einem abgeschnittenen Etikettfoto' — this is for photos with cropped edges, not full-label reading. However, no explicit when-to-use or when-not-to-use statement is given, and no sibling (e.g. the underline/treatment-bar reading tools) is named as the alternative once the crop turns out to be readable.

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