Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Dreame Kompakt-Luftreiniger TP10

tds_purchase_m_dreame_dreame_kompakt_luftreiniger_tp10
Read-onlyIdempotent

Recorded model Kompakt-Luftreiniger TP10. 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_kompakt_luftreiniger_tp10"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already cover the safety profile (read-only, non-destructive, idempotent, closed-world), so the description only needs to add context. It does add a meaningful assumption that the estimate mirrors the measured period's use and conditions, but it leaves the actual computed result and any output behavior unexplained.

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?

The description is short and front-loads the model identity, then adds one parameter instruction and one assumption. It is efficient, though the opening phrase "Recorded model" is awkward and does not immediately establish the tool's action.

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?

For a tool with five required numeric parameters, no output schema, and no schema descriptions, the definition is under-specified. It identifies the product and one assumption but does not explain what is being projected, the units involved, or how the inputs combine.

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 should carry the burden. It only gives guidance for offeredModel and does not explain measuredKwh, measuredDays, projectedDays, or tariffPerKwh, leaving most parameter semantics 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 identifies the exact model (Kompakt-Luftreiniger TP10) and implies an estimate is produced, but it never states a clear action such as "calculate projected energy consumption." It distinguishes this tool from siblings only by product name, not by an explicit verb or scope.

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 only guidance is parameter-oriented: use the seller's model field or exact variant name. It does not say when to choose this tool versus a sibling or the general climate-control quote tool, nor does it state any exclusions or prerequisites.

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.