Skip to main content
Glama

getecoback-raumklima

philips_airfryer_ungeteiltes_stueck_nennvolumen

Read-only

Ein unteilbares Stück mit dem einzelnen Korb vergleichen und Gesamtpfannenvolumen getrennt kennzeichnen — Check an indivisible volume against the stated vessel scope.

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": "<modell>",
      "unteilbar": "<unteilbar>",
      "volumen_l": "<volumen_l>"
    },
    "name": "philips_airfryer_ungeteiltes_stueck_nennvolumen"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständige deutsche Gerätevariante.
unteilbarYesMuss dieses Stück ungeteilt in ein Gefäß?
volumen_lYesUnabhängig bekanntes Volumen des ungeteilten Stücks in Litern, keine Schätzung aus dem Gesamtgewicht.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 comparison/labeling idea but does not explain what result is produced or how the 'kennzeichnen' should be interpreted.

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 definition is short, but the bilingual duplication and abstract phrasing make it harder to parse than necessary. It is not bloated, yet the single sentence does not front-load a clear action.

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

Completeness2/5

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

For a three-parameter check with no output schema, the description should clarify what the check returns and how to interpret the labeled volume. It does not do so, leaving a significant gap despite rich parameter schemas and read-only annotations.

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 all three parameters are already documented in the schema. The description adds no additional meaning about modell, unteilbar, or volumen_l beyond what the structured fields provide, making the baseline 3 appropriate.

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 an action (compare an indivisible piece, mark total pan volume separately) and a resource (vessel scope), but the phrasing is abstract and partly cryptic. It does not clearly distinguish this tool from the many Philips airfryer-related siblings, so the purpose remains only vaguely inferable.

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 when-to-use guidance, no exclusions, and no named alternative. The agent is left to infer the tool's role from a single ambiguous sentence.

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