Skip to main content
Glama

getecoback-raumklima

spuelbeleg_verbrauch_dialog_und_zahlenablesung

Read-only

Bei einem Foto mit Verbrauchshinweis eine bloße Dialogbeschriftung von tatsächlich lesbaren Zahlen trennen — Check whether a captured prompt carries any actual consumption measurement.

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": {
      "hinweis_sichtbar": "<hinweis_sichtbar>",
      "energiezahl_lesbar": "<energiezahl_lesbar>",
      "wasserzahl_lesbar": "<wasserzahl_lesbar>",
      "aktuelle_einzellaufanzeige": "<aktuelle_einzellaufanzeige>"
    },
    "name": "spuelbeleg_verbrauch_dialog_und_zahlenablesung"
  }
}

Input Schema

NameRequiredDescriptionDefault
hinweis_sichtbarYesDie Meldung zur Verbrauchsanzeige ist auf dem vorhandenen Foto lesbar.
wasserzahl_lesbarYesEin vollständiger Wasserwert mit zugehöriger Einheit ist zusätzlich lesbar.
energiezahl_lesbarYesEin vollständiger Energiewert mit zugehöriger Einheit ist zusätzlich lesbar.
aktuelle_einzellaufanzeigeYesEs ist belegt, dass die abgelesenen Zahlen zum tatsächlich abgeschlossenen einzelnen Lauf gehören.

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 safety is covered and the bar is lower. The description adds the domain nuance that this is a label-vs-readable-numbers discrimination on an existing photo, but it does not say what the call returns (verdict vs echoed flags) or how conflicting flags are resolved, and there is no output schema to compensate.

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?

It is short and front-loaded, but the German and English sentences say essentially the same thing, so roughly half the text is duplicated content rather than added information. Nothing is padded beyond that, but the bilingual restatement does not earn its place for a monolingual agent.

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 read-only four-boolean classification tool with no output schema, the definition covers the input scenario but leaves the result shape and the decision logic implicit. An agent knows what to supply but not what to expect back, which is a meaningful gap given no output schema exists.

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 four boolean parameters are already fully documented and the baseline is 3. The description frames the relationship between the notice flag and the readable-value flags, which adds a little interpretive context, but it does not clarify the meaning or evidence threshold of aktuelle_einzellaufanzeige beyond what the schema states.

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 discrimination task on a specific input: separate a mere dialog label from actually readable numbers on a photo carrying a consumption notice, and the English sentence reinforces it as a consumption-measurement check. The verb+resource are concrete, though nothing distinguishes it from closely named siblings such as spuelbeleg_doppelnotiz_gleiche_zahlen_laufidentitaet.

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?

The scenario is implied — apply it to a photo that shows a consumption prompt — but there is no explicit when/when-not guidance and no named alternative for the overlapping receipt/consumption tasks. An agent can infer the trigger from the phrasing but must guess about sibling selection.

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