Skip to main content
Glama

getecoback-raumklima

naturtrocknen_quadrat_striche_schatten

Read-only

Horizontale und senkrechte Linien, zwei Striche sowie die Schattendiagonale im Naturtrocknungsquadrat lesen — Decode flat or line drying, dripping wet and shade.

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": {
      "quelle": "<quelle>",
      "richtung": "<richtung>",
      "anzahl": "<anzahl>",
      "schattendiagonale": "<schattendiagonale>"
    },
    "name": "naturtrocknen_quadrat_striche_schatten"
  }
}

Input Schema

NameRequiredDescriptionDefault
anzahlYesAnzahl paralleler waagerechter oder senkrechter Linien.
quelleYesWo wurde das konkrete Zeichen gelesen? Eine Zuordnung zum Stück separat prüfen.
richtungYesLinien im Naturtrocknungsquadrat ohne Trommelkreis.
schattendiagonaleYesDiagonalen für Schatten an der vorgesehenen Ecke der Vorlage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 the specific semantic dimensions being decoded, but it does not explain return behavior, ambiguity handling, or how the readings combine into a result.

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

Conciseness4/5

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

The description is essentially one front-loaded sentence with a short English gloss, and it avoids unnecessary background. The bilingual duplication is slightly redundant but not wasteful enough to obscure the core purpose.

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?

For a four-required-parameter decoding tool with no output schema, the definition identifies the inputs being read but does not describe the returned interpretation or how ambiguous combinations are resolved. The fully documented schema compensates for much of the parameter detail, but the description remains thin on output semantics.

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 four enum parameters are already documented in the schema. The description reinforces the line/stroke/shadow-diagonal dimensions but does not add syntax or interpretation beyond the schema, and it does not mention the 'quelle' parameter.

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 states a specific action (lesen/Decode) and the exact symbol features involved: horizontal/vertical lines, two strokes, and the shadow diagonal in the Naturtrocknungsquadrat. It implicitly distinguishes this from the tumble-dryer sibling by naming the natural-drying square, though the bilingual phrasing is somewhat compressed.

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?

The description does not explicitly say when to use this tool versus alternatives, nor does it name any sibling or exclusion condition. The scope is implied by 'Naturtrocknungsquadrat', but an agent gets no direct routing guidance.

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