Skip to main content
Glama

getecoback-climate-weather

trocknerzeichen_kreis_im_quadrat_punkte

Read-only

Kreis im Quadrat mit einem oder zwei Punkten oder als durchgestrichenes Trocknerzeichen lesen — Decode normal, mild or prohibited drum drying.

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>",
      "zeichen": "<zeichen>"
    },
    "name": "trocknerzeichen_kreis_im_quadrat_punkte"
  }
}

Input Schema

NameRequiredDescriptionDefault
quelleYesWo wurde das konkrete Zeichen gelesen? Eine Zuordnung zum Stück separat prüfen.
zeichenYesGanzes Quadrat mit sichtbarem Kreis. Leeres Quadrat hier als „unklar“ eintragen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 and the bar is lower. The description adds real interpretive content by mapping the three glyph variants to permitted drying levels, which is behavior beyond the annotations. It does not say what the tool does with an ambiguous or empty square, leaving that to the schema.

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?

A single compact sentence, front-loaded with the visual description of the glyph before the English meaning gloss. No filler or redundant restatement of the tool name. The bilingual structure is slightly dense but each clause carries information.

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?

For a two-enum-parameter classifier with no output schema, the description supplies the domain meaning needed to call it correctly. The main residual gap is not stating how the result is expressed, but that is minor for such a narrow read-only tool.

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 both parameters are fully enumerated with per-value documentation, so the baseline is 3. The description mentions the one-dot/two-dot/struck variants, mildly echoing the 'zeichen' enum, but adds no extra meaning about 'quelle' or about how source attribution affects interpretation.

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 specific verb ('lesen'/'Decode') and a specific resource: the circle-in-square tumble-dry symbol with one dot, two dots, or a strike-through. It also gives the semantic mapping (normal / mild / prohibited drum drying), so an agent knows exactly which glyph family is being interpreted. It stops short of naming sibling symbols (e.g. the line-dry square) as an explicit contrast, which keeps it from a 5.

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: read this when the care label shows a circle inside a square. There is no explicit when-not clause and no pointer to the sibling tools that handle related laundry symbols such as naturtrocknen_quadrat_striche_schatten or buegelzeichen_punkte_dampf_normausgabe, so the agent must infer the routing itself.

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