Skip to main content
Glama

getecoback-climate-weather

philips_perfectcare_gewicht_handteil_station_verpackung

Read-only

Bei der PSG7140/70 ein persönlich gesetztes Gewichtslimit der tatsächlich bewegten Einheit zuordnen — Apply a personal weight budget to the handpiece, combined station or retail box.

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": {
      "psg7140_70_belegt": "<psg7140_70_belegt>",
      "bewegte_einheit": "<bewegte_einheit>",
      "eigenes_limit_kg": "<eigenes_limit_kg>"
    },
    "name": "philips_perfectcare_gewicht_handteil_station_verpackung"
  }
}

Input Schema

NameRequiredDescriptionDefault
bewegte_einheitYesWelche Einheit soll als Ganzes bewegt werden?
eigenes_limit_kgYesPersönliches Gewichtslimit für den Vergleich mit der Herstellerangabe.
psg7140_70_belegtYesIst der genaue /70 Code bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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. Beyond that, the description adds no behavioral context: it does not say whether this returns a comparison against the manufacturer figure, how the 'offen' unit is handled, or what the outcome of a budget assignment looks like.

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 model condition first. The German/English duplication is somewhat redundant but keeps it short and readable overall.

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?

With 3 required parameters fully documented and no output schema, the description is minimally adequate. It is thin given the nontrivial required boolean confirmation and the comparison intent that only surfaces in the schema.

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, and the baseline of 3 applies. The description echoes the enum choices (handpiece, combined station, retail box) but adds no semantics for the limit range or the 'belegt' gate beyond what the schema states.

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 states a specific verb ('zuordnen' / 'Apply') and a specific resource ('persönlich gesetztes Gewichtslimit' mapped to handpiece, station or retail box), and scopes it to the PSG7140/70 model. It is clear what the tool does, though it never names or contrasts a sibling tool.

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?

The model reference PSG7140/70 implies applicability, but there is no explicit when-to-use or when-not guidance, no alternative named, and nothing about what to do if the required 'psg7140_70_belegt' confirmation is false.

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