Skip to main content
Glama

getecoback-climate-weather

buegelzeichen_punkte_dampf_normausgabe

Read-only

Bügeleisen mit Punkten, neuem Ohne-Dampf-Zeichen oder Kreuz lesen und Celsius nur bei belegter ISO-Ausgabe zuordnen — Read ironing heat and steam markings with edition-aware ceilings.

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>",
      "eisen": "<eisen>",
      "normausgabe": "<normausgabe>"
    },
    "name": "buegelzeichen_punkte_dampf_normausgabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
eisenYesVollständige Zeichenvariante der passenden Legende.
quelleYesWo wurde das konkrete Zeichen gelesen? Eine Zuordnung zum Stück separat prüfen.
normausgabeYesZu diesem Zeichen belegte Legende.

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?

The readOnlyHint and openWorldHint annotations already establish safe local reading. The description adds the domain-specific constraint that Celsius is assigned only with documented ISO output, but does not explain output shape or edge-case handling.

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 definition is a single compact sentence with the purpose front-loaded. The bilingual duplication and the phrase 'edition-aware ceilings' slightly reduce crispness but do not add substantial waste.

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?

All three required parameters have full schema coverage and annotations cover the safety profile. The description states the key edition condition, but it does not describe the return value or the effect of source and uncertain-symbol parameters, leaving some contextual gaps.

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 the enum descriptions already document all three parameters. The description maps the symbol variants to the heat/steam reading purpose and ties normausgabe to Celsius assignment, but adds limited meaning 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 description names a specific verb and resource: reading iron heat and steam markings, including dot, new no-steam, and crossed variants. It also mentions the edition-aware Celsius mapping, but does not explicitly distinguish the tool from siblings.

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?

It gives an explicit condition for Celsius assignment: only when an ISO edition is documented. However, it does not state when to use this tool versus alternatives or any when-not 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