Skip to main content
Glama

getecoback-raumklima

bosch_twk8613p_doppelwand_oberflaeche_beruehrbarkeit

Read-only

Prüft, was das Bosch-Doppelwand-Gehäuse zu reduzierter Außentemperatur belegt und ob damit eine konkrete berührbare Stelle nachgewiesen ist — Distinguish the double-wall feature from a measured touch-temperature result.

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": {
      "modell_genau": "<modell_genau>",
      "anforderung": "<anforderung>"
    },
    "name": "bosch_twk8613p_doppelwand_oberflaeche_beruehrbarkeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
anforderungYesBenötigter Nachweis.
modell_genauYesTWK8613P laut deutschem Produktblatt und Gerät eindeutig.

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 safety profile is covered. The description adds that this is an evidence/proof query (what the construction 'belegt' versus what is 'nachgewiesen'), which is meaningful context beyond the annotations. It does not say what the response looks like or how a negative finding is expressed, and no output schema exists to fill that gap.

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?

Single sentence with the purpose front-loaded, which is good, but the German clause is convoluted ('was ... belegt und ob damit ... nachgewiesen ist') and the German/English mix reads as a stitched-on afterthought rather than tight guidance.

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 a small, read-only, two-parameter evidence check with full schema coverage and annotations, and the description covers its intent. Because there is no output schema, the description should say what a result looks like (a proof, a confirmed touch point, or neither), and that is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, making 3 the baseline. The description does add real value by framing the exact distinction the 'anforderung' enum encodes (doppelwand_konstruktionsmerkmal vs. temperatur_an_kontaktstelle), telling the agent which proof type it is selecting between. It says nothing extra about the 'modell_genau' identity flag beyond what the schema states.

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?

States a specific verification verb ("Prüft") against a specific resource (the Bosch double-wall housing / its reduced exterior temperature), and adds the key epistemic twist that it checks what the evidence actually proves about a touchable surface. It is clear what the tool answers, but it never names or contrasts any sibling (e.g. the many other 'oberflaeche' tools), so an agent must infer routing from the name alone.

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 'Distinguish the double-wall feature from a measured touch-temperature result' clause implies when the tool is relevant, but it reads as a self-description rather than a when-to-use/when-not rule. No prerequisites (e.g. product sheet present) or exclusions against alternatives are given.

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