Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Dreame Luftreiniger TP20

tds_purchase_m_dreame_dreame_luftreiniger_tp20
Read-onlyIdempotent

Recorded model Luftreiniger TP20. 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_luftreiniger_tp20"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety behavior is covered structurally. The description adds one genuinely useful piece of non-annotated context: the projection assumes the same usage conditions as the measured period. It does not say whether results are persisted, what the response contains, or how the projection is derived from the five inputs.

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 description is short and front-loaded, with no filler beyond the first sentence. However, that first sentence is close to a restatement of the title, so a meaningful share of the limited text is not earning its place. Structure is acceptable but not information-dense.

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

Completeness5/5

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

There is no output schema, but the description honestly states the estimation basis (same use and conditions as the measured period), which is the key caveat for interpreting results. Nothing essential for correct invocation is withheld, aside from parameter-level units that the schema itself omits.

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% across five required parameters, so the description must carry the meaning and largely does not. It hints at offeredModel ("seller's model field or exact variant name") and obliquely at measuredDays ("your measured period"), but measuredKwh, projectedDays and tariffPerKwh are never mentioned — leaving units, currency and horizon semantics entirely undocumented.

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 product ("Luftreiniger TP20") and implies an energy estimate through "The estimate assumes the same use and conditions as your measured period," but never states a verb or object for the operation itself. The first sentence, "Recorded model Luftreiniger TP20," mostly restates the title rather than explaining what the tool computes or returns. An agent must infer from the name prefix (tds_purchase_m) that this projects energy consumption for this specific appliance.

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 guidance about one parameter's value format, not about when to choose this tool. There is no indication of when this per-product tool applies versus the dozens of near-identical sibling product tools or versus quote-level tools like tds_quote_climate_control. The only usable takeaway is that the tool is model-scoped, which the name already conveys.

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.