Skip to main content
Glama

getecoback-climate-weather

bosch_sks62e32eu_geraeuschklasse_und_energieklasse

Read-only

Trennt die Geräusch-Effizienzklasse von der Energieklasse und grenzt den Schallleistungswert vom Küchenmesswert ab — Keep the noise class, energy class and sound-power declaration distinct.

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": {
      "gebrauch": "<gebrauch>",
      "modell_de_belegt": "<modell_de_belegt>"
    },
    "name": "bosch_sks62e32eu_geraeuschklasse_und_energieklasse"
  }
}

Input Schema

NameRequiredDescriptionDefault
gebrauchYesWelche Aussage soll aus der Quelle übernommen werden?
modell_de_belegtYesDer Quellenwert gehört zur exakten deutschen Modellangabe.

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 the safety profile is covered. The description adds a domain constraint (keep noise class, energy class and sound-power declaration distinct) that goes beyond the annotations, but it says nothing about what the call returns or how the distinction is expressed.

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?

The statement is short and front-loaded, but the English clause is a near-verbatim restatement of the German one, so half the text adds no new information. It is not padded, but it is also not maximally efficient.

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 two-parameter, read-only, closed-world tool with full schema coverage and no output schema, the description supplies the domain rule but omits what result to expect. It is adequate but leaves a real gap about the tool's effect.

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 both parameters carry their own descriptions and an enum, so the schema does the heavy lifting. The description adds no syntax, format or interpretation detail beyond the conceptual framing already implied by the parameter names.

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 the domain concepts (Geräusch-Effizienzklasse, Energieklasse, Schallleistungswert, Küchenmesswert) and states that they must be kept apart, but the operative verb 'trennt/abgrenzt' never resolves into a concrete action or output an agent can predict. It reads more like a rule reminder than a statement of what the tool does, and it does not differentiate itself from the many sibling disambiguation tools.

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 explicit guidance on when to call this tool versus the numerous sibling tools, nor any exclusion or precondition. The 'gebrauch' enum ('etikettvergleich' vs 'pegel_am_eigenen_platz') hints at two usage contexts, but the description never explains which situation selects this tool.

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