Skip to main content
Glama

getecoback-raumklima

bosch_bfl524ms0_inverter_maximalleistung_dauer_keine_garprognose

Read-only

Bosch Inverter-Angabe zur Abregelung bei längerem Betrieb auf den genauen Begriff und das Modell begrenzen — Interpret the model-specific long-run power reduction without inventing timing.

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": {
      "datenblatt_belegt": "<datenblatt_belegt>",
      "beobachtung": "<beobachtung>"
    },
    "name": "bosch_bfl524ms0_inverter_maximalleistung_dauer_keine_garprognose"
  }
}

Input Schema

NameRequiredDescriptionDefault
beobachtungYesWelche Aussage wurde dokumentiert?
datenblatt_belegtYesE-Nr mit Index und Modellzuordnung des konkreten Herstellernachweises stimmen überein?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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. The description contributes one real behavioral point — that the interpretation must not fabricate timing and must be bounded to the exact term and model — which is meaningful context. However, with no output schema, it never says what the result looks like or how the evidence check is reported, so the burden is only partly carried.

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 a single short sentence, so there is little waste, and the scope constraint is placed first. But the bilingual construction is hard to parse and mixes two registers, which costs clarity rather than buying precision.

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 tool is simple (two required parameters, both documented, read-only, closed-world), which lowers the bar. Still, with no output schema the description should indicate what interpreting the documented observation yields, and it offers no usage conditions — a minimum-viable rather than complete definition.

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 coverage is 100%: both parameters carry descriptions and 'beobachtung' has a four-value enum, so the schema does the work. The description's phrase about limiting to the exact term and model loosely echoes 'datenblatt_belegt' (E-Nr index and model match) but adds no new syntax or interpretation beyond what the schema states. 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 topic (Bosch inverter derating during longer operation) and a verb (interpret), and it flags the scope limit of the exact term and model. But the German half is cryptic ('auf den genauen Begriff und das Modell begrenzen') and the English half is a constraint rather than a statement of what the tool returns, so an agent can't tell this apart from siblings like bosch_bfl524ms0_watt_anschlusswert_und_garleistung or bosch_bfl524_kuehlgeblaese_nachlauf_kein_weitergaren_beleg without inspecting the schema.

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 when-to-use or when-not-to-use guidance and no mention of any alternative tool. The only routing signal is the negative instruction 'without inventing timing', which constrains the answer's content rather than telling the agent when this tool is the right choice.

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