Skip to main content
Glama

getecoback-raumklima

philips_hd9875_90_gewichtsaussage_lebensmittelbezug

Read-only

Den 2-kg-Wert des HD9875/90 nur mit der klar belegten Beispielkategorie vergleichen — Keep the documented frozen-fries mass claim tied to its stated example.

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_belegt": "<modell_belegt>",
      "bezug": "<bezug>",
      "verglichen_kg": "<verglichen_kg>",
      "herkunft_gleich": "<herkunft_gleich>"
    },
    "name": "philips_hd9875_90_gewichtsaussage_lebensmittelbezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
bezugYesKategorie des zu vergleichenden Angebots oder Nachweises.
modell_belegtYesIst die genaue deutsche Variante HD9875/90 anhand ihrer eigenen Gerätekennzeichnung bestätigt?
verglichen_kgYesZu prüfender genannter Gewichtsvergleich in kg.
herkunft_gleichYesBezieht sich die Zahl auf genau dieses Lebensmittel bei diesem einzelnen Gerät und auf die Kapazitätsangabe, nicht auf ein Gefäßvolumen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 the claim must remain tied to its stated example, but says nothing about what a failed or ambiguous check yields, so it contributes only modest behavioral context.

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?

It is a single short, front-loaded statement, but the German and English halves restate the same constraint rather than complementing each other, so roughly half the text is redundant.

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?

Four fully described required parameters plus read-only annotations mean an agent can construct a call without further help. There is no output schema and the description does not indicate what the verdict looks like, which is a minor residual gap for a check-style 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%, so every parameter is already documented, including the bezug enum and the kg bounds. The description reinforces the example-category linkage that maps to bezug but adds no syntax or interpretation beyond the schema.

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 resource (the 2-kg value of the HD9875/90) and a comparison action, and pins it to the documented frozen-fries example. But what the tool actually produces or decides is never stated, and there is no explicit differentiation from the many similarly named Philips verification siblings.

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?

It gives one usage constraint — compare only against the clearly documented example category — which implies when the tool is applicable. It does not name an alternative tool or state when not to use it, so guidance is implied rather than explicit.

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