Skip to main content
Glama

getecoback-climate-weather

bosch_bfl524_automatik_signal_waehrend_programm

Read-only

Ein Signal mit weiterlaufendem oder angehaltenem AutoPilot von einem bestätigten Programmende trennen — Distinguish a mid-programme intervention signal from a confirmed finish.

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_belegt": "<handbuch_belegt>",
      "beobachtung": "<beobachtung>",
      "signal_beobachtet": "<signal_beobachtet>",
      "restzeit_positiv": "<restzeit_positiv>"
    },
    "name": "bosch_bfl524_automatik_signal_waehrend_programm"
  }
}

Input Schema

NameRequiredDescriptionDefault
beobachtungYesWann wurde das Signal beobachtet?
handbuch_belegtYesGenaue deutsche Geräteausführung BFL524MS0 und Anwendbarkeit des Dokuments 9001610906_F am Gerät geklärt?
restzeit_positivYesWar eine positive Restzeit noch ablesbar?
signal_beobachtetYesAkustisches Signal am konkreten Lauf tatsächlich beobachtet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 agent knows this is a safe, closed-world inspection. The description adds nothing about how the distinction is made, what the verdict depends on, or what happens with ambiguous inputs — though as a read-only diagnostic the risk is low. Useful context, such as the manual-verification prerequisite, lives only in the schema descriptions.

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, front-loaded sentences with no padding. The German original plus English rendering is mildly redundant but aids cross-language agents and does not obscure the intent.

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?

With four required parameters, no output schema, and a purely diagnostic purpose, the description should hint at how the inputs combine into a verdict or what 'unklar' implies. It conveys the goal but not the decision logic, leaving the agent to infer how the answer is derived.

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 four parameters (beobachtung enum, handbuch_belegt, restzeit_positiv, signal_beobachtet) are already documented in the schema. The description contributes no additional parameter meaning, which is the baseline expectation when the schema does the heavy lifting.

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 states a specific cognitive task: separating a mid-programme intervention signal (AutoPilot continuing or paused) from a confirmed programme end. That is more precise than a tautology and lets an agent recognize it as a diagnostic decision step rather than an action. It does not name or differentiate itself from any sibling tool, keeping 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?

The when-to-use condition is only implied: apply this when a signal was observed and the question is whether the programme actually finished. There is no explicit statement of when not to use it, no mention of alternatives (e.g. the sibling tools covering coolant-fan run-on or AutoPilot portioning), and no sequencing guidance. Usage is inferable but not spelled out.

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