Skip to main content
Glama

getecoback-raumklima

waesche_trocknungskosten

Read-only

Messwerte für zwei Trocknungswege vergleichen — Compare measured energy costs for equally dry laundry.

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": {
      "dryer": "<dryer>",
      "dehum": "<dehum>",
      "comparable": "<comparable>",
      "price": "<price>"
    },
    "name": "waesche_trocknungskosten"
  }
}

Input Schema

NameRequiredDescriptionDefault
dehumYesEntfeuchter: gemessene kWh pro Ladung.
dryerYesTrockner: kWh pro Ladung.
priceYesEigener Strompreis in EUR/kWh.
comparableYesGleiche Wäschemenge und Endtrockenheit erreicht?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that inputs are measured values and that the comparison is only meaningful at equal dryness, but it never says what the tool produces (cost per load, delta, verdict), which matters because there is no output schema.

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?

Two short sentences with the core action front-loaded and no filler. The bilingual restatement is mildly redundant but serves as a disambiguation aid rather than padding.

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?

For a four-required-parameter calculation tool with no output schema, the description covers inputs and the validity condition but leaves the result shape entirely unspecified. An agent knows how to call it but not what it will get back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description goes slightly beyond by framing the comparison as requiring equal dryness, reinforcing the meaning of the 'comparable' boolean. It does not clarify units or bounds for dryer/dehum/price, but the schema already does that.

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?

States a specific verb (compare) and resource (measured energy costs for two drying paths), and the German/English pair makes the intent unambiguous. It does not name or distinguish itself from near siblings such as entfeuchter_energie_je_liter or geraetewechsel_rechnen, so an agent must infer the boundary.

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?

The phrase 'for equally dry laundry' implies the precondition that makes a comparison valid, which maps to the required 'comparable' flag. However, there is no explicit when-to-use/when-not guidance and no pointer to an alternative tool for a single-device energy figure.

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