Skip to main content
Glama

getecoback-climate-weather

brita_aktivierung_trichterfuellung_nicht_liter

Read-only

Trichterfüllungen im MAXTRA PRO Kannenhandbuch von einer Literangabe aus der unterstützenden FAQ unterscheiden — Reconcile the different first-use evidence units.

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": {
      "handbuch_passt_zur_kanne": "<handbuch_passt_zur_kanne>",
      "beleg_einheit": "<beleg_einheit>",
      "vollstaendige_trichterfuellungen": "<vollstaendige_trichterfuellungen>",
      "volumen_l": "<volumen_l>"
    },
    "name": "brita_aktivierung_trichterfuellung_nicht_liter"
  }
}

Input Schema

NameRequiredDescriptionDefault
volumen_lYesSeparat gemessene Anfangsmenge in Litern, bei nicht belegt 0.
beleg_einheitYesWas wurde für dieses Exemplar tatsächlich protokolliert?
handbuch_passt_zur_kanneYesIst die verlinkte MAXTRA PRO Kannenanleitung genau für die verwendete Kanne und Kartusche bestätigt?
vollstaendige_trichterfuellungenYesGezählte vollständig durchgelaufene erste Trichterfüllungen, bei nicht belegt 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered structurally. Beyond that the description adds no behavioral context: it says nothing about what happens when the manual and FAQ disagree, whether conflicting inputs are rejected, or what the response contains. With annotations present the bar is lower, but nothing here clears it.

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?

Two short sentences with the domain constraint front-loaded, which is good structure for an instruction-first agent. The English clause largely restates the German one, so there is minor redundancy, but nothing is padded or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a read-only reconciliation of four required evidence parameters with no output schema, so the description is the only place an agent could learn what the tool produces — and it says nothing about the result shape or verdict. For a tool whose entire value is resolving conflicting evidence units, the omission of the reconciliation outcome is a substantive gap.

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 each parameter already documents its meaning (volumen_l as 'separately measured starting quantity in liters, 0 if not evidenced', beleg_einheit as what was actually logged). The description's mention of 'Literangabe aus der FAQ' versus 'Trichterfüllungen im Handbuch' loosely maps to volumen_l and vollstaendige_trichterfuellungen but adds no syntax, defaults, or interaction rules beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete domain (MAXTRA PRO jug manual vs. supporting FAQ) and the two evidence units being separated (funnel fillings vs. liters), and the English half states the intent as 'reconcile'. However, the verb 'reconcile/unterscheiden' stays abstract: an agent cannot tell whether the tool converts units, returns a verdict on consistency, or merely records the reconciled evidence. No sibling is named to sharpen the boundary.

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?

There is no explicit when-to-use or when-not-to-use statement and no mention of an alternative tool. The scenario is only faintly implied by 'first-use evidence units', so an agent must infer the triggering condition from the parameter names rather than from the description.

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