Skip to main content
Glama

getecoback-climate-weather

spuelstatus_ende_um_timer_ende_zeittext_unterscheiden

Read-only

Eine protokollierte Anzeige Ende um als Timerwunsch vom Marker Ende unterscheiden — Identify whether a time label is a schedule, estimate or observed end.

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": {
      "textart": "<textart>",
      "quelle_und_geraet_bestaetigt": "<quelle_und_geraet_bestaetigt>",
      "am_lauf_gelesen": "<am_lauf_gelesen>"
    },
    "name": "spuelstatus_ende_um_timer_ende_zeittext_unterscheiden"
  }
}

Input Schema

NameRequiredDescriptionDefault
textartYesVollständig gelesener Text oder eindeutig belegtes Feld.
am_lauf_gelesenYesDer Text wurde für den bezeichneten Lauf tatsächlich abgelesen.
quelle_und_geraet_bestaetigtYesAngezeigtes Feld und genaue Anleitung für dieses Gerät verbunden?

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 that this is a classification of label types, but it does not explain what the classification returns, how 'nicht_eindeutig' should be handled, or any operational limits. With annotations carrying safety, this is adequate but thin.

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 compact and front-loads the core distinction, with a short English gloss after the German phrase. The bilingual duplication is slightly redundant but not wasteful, and no sentence is extraneous.

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?

The description explains the classification purpose but does not describe the return value, despite there being no output schema. It also does not elaborate on why the two confirmation booleans are required or what happens with ambiguous inputs. The schema covers the parameters, so the definition is usable but leaves gaps around output and ambiguity handling.

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 three parameters and the enum values are already documented in the input schema. The description mentions distinguishing schedule, estimate and observed end, which loosely maps to the enum, but adds no additional semantics for 'textart', 'am_lauf_gelesen' or 'quelle_und_geraet_bestaetigt' beyond what the schema provides.

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 English sentence states a specific classification task: identify whether a time label is a schedule, estimate or observed end. The German clause adds the distinction between an 'Ende um' timer request and a plain 'Ende' marker. It does not differentiate this tool from any sibling, but the core purpose is clear enough to select it.

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 definition implies the tool is used when an 'Ende um' label must be distinguished from an end marker, but it gives no explicit when-to-use or when-not-to-use guidance. It also names no alternative sibling tool, leaving the agent to infer routing from the description alone.

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