Skip to main content
Glama

getecoback-climate-weather

bosch_sks62e32eu_programm_oder_zusatzfunktion

Read-only

Ordnet einen angebotenen Betriebsnamen als Prüfprogramm, anderes Programm oder Zusatzfunktion ein — Classify a named mode as the Eco test program, another program or an option.

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": {
      "bezeichnung": "<bezeichnung>",
      "modell_de_belegt": "<modell_de_belegt>"
    },
    "name": "bosch_sks62e32eu_programm_oder_zusatzfunktion"
  }
}

Input Schema

NameRequiredDescriptionDefault
bezeichnungYesGenaue Bezeichnung aus der deutschen Quelle.
modell_de_belegtYesUnterlage passt genau zu SKS62E32EU.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the three-way classification taxonomy, which is useful context, but it says nothing about how 'modell_de_belegt' changes the outcome or what form the classification result takes.

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?

A single front-loaded sentence with the category list at the end; nothing extraneous. The German/English duplication adds length without new meaning, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter classification tool with no output schema, the description conveys the input semantics and the possible classification outcomes, which is most of what an agent needs. The remaining gap is how the 'modell_de_belegt' flag influences the verdict.

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% — both parameters carry descriptions and 'bezeichnung' has a 9-value enum — so the schema already does the parameter work. The prose adds no syntax, format, or edge-case guidance beyond what the schema states, which is the baseline case for a 3.

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 names a specific action (classify/assign a named operating mode) and the resulting categories (Eco test program, other program, option), so the agent knows exactly what the tool produces. It does not compare itself to any sibling, but the purpose is unambiguous from the verb+resource pairing.

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?

Usage is only implied: the agent can infer it should call this when it has a Betriebsname taken from the German source and wants it categorized. There is no explicit when-to-use statement, no mention of prerequisites, and no routing to an alternative 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