Skip to main content
Glama

getecoback-raumklima

braun_mq7035xbi_mc_zutatenmenge_markierung

Read-only

Vergleicht beim Braun mc-500-Zerkleinerer konkrete Zutatenmassen und die sichtbare Max-Markierung — Compare ingredient weights and the visible max line for the Braun mc 500 ml chopper.

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": {
      "mc_mit_universalmesser_bestaetigt": "<mc_mit_universalmesser_bestaetigt>",
      "zutat": "<zutat>",
      "masse_g": "<masse_g>",
      "max_markierung_eingehalten": "<max_markierung_eingehalten>"
    },
    "name": "braun_mq7035xbi_mc_zutatenmenge_markierung"
  }
}

Input Schema

NameRequiredDescriptionDefault
zutatYesKlar abgebildete Zutat in der Tabelle.
masse_gYesGewogene Netto-Zutat in Gramm.
max_markierung_eingehaltenYesSichtbare Max-Markierung für diese Befüllung eingehalten?
mc_mit_universalmesser_bestaetigtYesMQ 7035 XBI mit zugehörigem mc und Universalmesser bestätigt.

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 the safety profile is covered and the description's silence on side effects is not a defect. The description adds the comparison criterion (visible max marking, 500 ml vessel) but says nothing about what a comparison result looks like or how an "offen" max-marking state is handled.

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?

The content is short and front-loaded, but the same sentence is stated twice in German and English, which doubles length without adding information. The bilingual duplication costs space that could have carried return-value or usage detail.

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?

There is no output schema, so the description should convey what the comparison yields, yet it never says whether the result is a verdict, a delta, or a flag. For a four-required-parameter validation tool with an "offen" branch in the max-marking enum, the description is adequate but leaves the agent guessing about the outcome.

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% with documented enums for zutat and max_markierung_eingehalten, so the schema carries parameter meaning on its own. The description only echoes two of the four inputs (mass and max marking) and adds no syntax, units, or edge-case guidance beyond that.

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 ("Vergleicht"/"Compare") and specific resources (concrete ingredient weights and the visible max line) tied to a named device, the Braun mc-500 chopper, so an agent can tell this is a max-fill check rather than a generic lookup. It does not explicitly differentiate itself from any of the many sibling Braun chopper tools, which keeps it below 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: the agent must infer that this is the tool to call when a weighed ingredient amount needs to be checked against the visible max marking. There is no statement of when not to use it and no reference to any alternative sibling tool.

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