Skip to main content
Glama

getecoback-climate-weather

bosch_tat8613_schlitzanzahl_scheibenmass_abgrenzen

Read-only

Zwei Röstschlitze von belegten Innenmaßen für eine Brotscheibe unterscheiden — Check slot count and distinguish it from fit evidence.

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_de_bestaetigt": "<modell_de_bestaetigt>",
      "scheiben": "<scheiben>",
      "eigene_passprobe": "<eigene_passprobe>"
    },
    "name": "bosch_tat8613_schlitzanzahl_scheibenmass_abgrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
scheibenYesZahl der einzelnen Brotscheiben für einen gemeinsamen Durchgang.
eigene_passprobeYesSicher beobachteter früherer Passzustand mit derselben Brotsorte und Dicke.
modell_de_bestaetigtYesBosch TAT8613 und deutsche Herstellerunterlagen am betreffenden Gerät oder Angebot bestätigt?

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 the tool read-only and closed-world. The description adds the conceptual separation between slot count and fit evidence, but does not disclose what the check returns or how the inputs drive the result.

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?

The description is very short and front-loads the purpose, with the English clause clarifying the German. The bilingual duplication is slightly redundant but not wasteful.

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 tool with three required parameters and no output schema, the description is minimally adequate: it identifies the check but leaves the return value and the role of each input implicit. An agent would need to infer what the tool actually returns.

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%, so all three parameters are fully documented in the schema. The description adds no further meaning about how scheiben, eigene_passprobe, and modell_de_bestaetigt interact.

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 check: distinguishing two toasting slots from evidence about whether a bread slice fits. The bilingual phrasing makes the resource clear, though it does not name any sibling tool.

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?

Use is implied: check slot count rather than conflate it with fit evidence. However, there is no explicit when-to-use guidance, no prerequisites, and no routing to alternatives among the many Bosch TAT8613 siblings.

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