Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Dreame Luftbefeuchter H40

tds_purchase_m_dreame_dreame_luftbefeuchter_h40
Read-onlyIdempotent

Recorded model Luftbefeuchter H40. 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_luftbefeuchter_h40"
  }
}

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?

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one piece of real behavioral context beyond that: the projection assumes the same usage conditions as the measured period, which tells the agent how to interpret the result. It says nothing further about units, precision, or what is returned, which keeps this at a middling score.

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 filler, which is good. But the opening fragment 'Recorded model Luftbefeuchter H40' restates the title without adding information, and the most important operational statement — that this computes an estimate — is buried at the end rather than front-loaded.

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-parameter calculator with no output schema and no parameter descriptions, yet the description never explains units (kWh, day counts, tariff currency), the arithmetic relationship between measured and projected values, or what the response contains. For a projection tool whose whole value is the numeric result, the definition leaves too much for the agent to assume.

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 bears the full burden. It only illuminates offeredModel ('seller's model field or exact variant name') and gestures at measuredKwh/measuredDays through 'measured period'; the meaning and units of projectedDays and tariffPerKwh (currency, per-kWh basis) are left entirely undocumented in both schema and description.

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 identifies the specific product variant ('Luftbefeuchter H40') and, via 'The estimate assumes the same use and conditions as your measured period,' hints that this produces an energy projection. However, it never states a clear verb+resource such as 'projects annual energy use for this humidifier,' so the actual function must be inferred from the name and title rather than read from the description. It does at least identify which product variant this tool is for, which is how it differs from its many siblings.

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, not usage guidance; there is no statement about when to pick this tool over a generic option such as tds_quote_climate_control or over a different product-variant sibling. No prerequisites, no exclusions, no conditions are given. An agent must guess that this is the H40-specific entry point.

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.