Skip to main content
Glama

getecoback-climate-weather

bosch_ii_m_thread_zusatzbaustein

Read-only

Ermittle den noch fehlenden Baustein für die direkte Matter-Einbindung beim Bosch II [+M] — Identify the missing component for direct Matter setup of Bosch II [+M]

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": {
      "plus_m_am_angebot": "<plus_m_am_angebot>",
      "matter_controller_eingerichtet": "<matter_controller_eingerichtet>",
      "controller_thread": "<controller_thread>",
      "externer_border_router": "<externer_border_router>"
    },
    "name": "bosch_ii_m_thread_zusatzbaustein"
  }
}

Input Schema

NameRequiredDescriptionDefault
controller_threadYesDer Controller hat integrierte Thread-Kommunikation
plus_m_am_angebotYesDas Angebot nennt die [+M]-Variante ausdrücklich
externer_border_routerYesPassender separater Thread Border Router bestätigt
matter_controller_eingerichtetYesMatter Controller und dessen App sind bereits eingerichtet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 and locality are covered without description help. The description adds only the notion that the result is the *missing* prerequisite, without saying how conflicting inputs are resolved or what form the answer takes. With annotations carrying the safety profile, this modest added context supports a 3.

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, front-loaded with the purpose, with no filler. The German/English duplication is a small redundancy but keeps the tool accessible to either audience and costs little.

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 four-required-parameter decision tool with rich enum schemas and read-only annotations, the definition is nearly adequate. However, there is no output schema and the description does not say what the agent receives back (a named missing step, a boolean, a next action), which is the key unanswered question for a diagnostic tool.

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 every parameter carries an enum or boolean with a German gloss, so the schema does the explanatory work. The description adds no meaning about how each input (e.g. dreiwerte 'belegt/ausgeschlossen/offen') is combined or weighted; baseline 3 applies.

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 gives a specific verb+resource: determine the still-missing building block for direct Matter integration of the Bosch II [+M]. It is clear this is a diagnostic/advisory check rather than a data retrieval, though 'Baustein' (component/step) stays abstract about what exactly is returned.

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 statement of when to use this tool, no preconditions, and no exclusions or alternatives among the many sibling diagnostic tools. The scenario (Bosch II [+M] Matter onboarding) is implied by the name only, leaving the agent to infer the trigger condition.

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