Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Dreame W20 Heizgerät

tds_purchase_m_dreame_dreame_w20_heizgerat
Read-onlyIdempotent

Recorded model W20 Heizgerät. Use the seller’s model field or exact variant name. The estimate assumes the same use and conditions as your measured period.

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": {
      "offeredModel": "<offeredModel>",
      "measuredKwh": "<measuredKwh>",
      "measuredDays": "<measuredDays>",
      "projectedDays": "<projectedDays>",
      "tariffPerKwh": "<tariffPerKwh>"
    },
    "name": "tds_purchase_m_dreame_dreame_w20_heizgerat"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds one genuine behavioral caveat — the projection assumes the same usage conditions as the measured period — which is real value beyond the annotations. It still does not say what is returned (cost? kWh?) or how the projection is computed.

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?

Three short sentences with no padding, and the product identification is front-loaded. However, the first sentence is a fragment with no operation verb, so the brevity comes at the cost of specification rather than being purely efficient.

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?

This is a five-required-parameter calculation tool with no output schema and no parameter documentation, so the description should explain the inputs, the projection logic and what the result represents. It supplies only a model-identification hint and an assumption caveat, leaving an agent unable to confidently call it or interpret the result.

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

Parameters2/5

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

Schema description coverage is 0% for all five required numeric parameters, so the description carries the full burden. It only clarifies offeredModel (use the seller's model field or exact variant name) and vaguely ties measuredDays to projectedDays; measuredKwh, tariffPerKwh and the meaning/units of projectedDays are left undocumented in both places.

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 a specific product ("model W20 Heizgerät") and hints at an estimate via "The estimate assumes the same use and conditions as your measured period," but never states a verb or the actual operation (projecting measured kWh/days to a projected period at a tariff). "Recorded model" is a fragment that could be read as writing a record or as identifying the measured device, so the agent must infer the purpose from the parameter names.

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?

"Use the seller's model field or exact variant name" is input guidance for one parameter, not when-to-use guidance. There is no statement of when this tool applies versus the many sibling product tools, no prerequisites, and no exclusions.

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.