Skip to main content
Glama

getecoback-raumklima

philips_buegeldampf_dauerstoss_druck_vergleichsart

Read-only

Je nach Messgröße die deutschen /80- und /70-Modellangaben für Durchfluss, Dampfstoß und Druck getrennt vergleichen — Compare matching steam specification types without equating different units.

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": {
      "typenschild": "<typenschild>",
      "messgroesse": "<messgroesse>",
      "angebotszahl": "<angebotszahl>"
    },
    "name": "philips_buegeldampf_dauerstoss_druck_vergleichsart"
  }
}

Input Schema

NameRequiredDescriptionDefault
messgroesseYesBezug der zu prüfenden Zahl.
typenschildYesVariante mit bestätigtem Schrägstrich-Suffix.
angebotszahlYesIm Angebot genannte Zahl entsprechend dem angegebenen Bezug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, closed-world operation, so the description's bar is lower. The description usefully adds that measurement types must be compared separately and units must not be equated, but it does not explain the response shape or how mismatches are handled.

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 definition is compact and front-loads the comparison behavior with no filler. The bilingual phrasing is slightly redundant, but it does not obscure the core instruction.

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 input schema is fully documented and annotations cover safety, but there is no output schema. The description does not state what the comparison returns, how results are structured, or what happens with incompatible inputs, leaving a meaningful gap for an agent invoking the 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 both enum parameters are already documented in the schema. The description reinforces that comparison depends on the measurement quantity and model type, but it adds no syntax or value details beyond what the schema provides.

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, 'vergleichen', and identifies the resources: the German /80 and /70 model specifications for flow, steam burst, and pressure. It also clarifies that comparison happens separately by measurement type, but it does not explicitly distinguish this tool from similarly named sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the key usage condition: compare according to the measurement quantity and do not equate different units. This gives clear operational context, though it does not name when not to use the tool or point to alternatives.

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