Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Blueair DustMagnet™ 5210i

tds_purchase_m_blueair_dustmagnet_5240i_copy
Read-onlyIdempotent

Recorded model DustMagnet™ 5210i. 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_blueair_dustmagnet_5240i_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact: the estimate assumes the same use and conditions as the measured period. It does not say whether anything is persisted server-side ("Recorded" implies storage despite readOnlyHint) or how the tariff applies.

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, but the lead sentence is redundant model-name restatement while the actual purpose is buried at the end. Front-loading is backwards relative to what an agent needs to route the call.

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

Completeness4/5

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

For a five-required-parameter projection tool with no output schema and no parameter documentation, the description leaves the core computation (kWh/day extrapolation and tariff multiplication) and four of five inputs unspecified. That is a meaningful gap for a tool the agent must fill correctly on the first try.

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 carries the full burden and largely fails it. Only offeredModel gets any clarification; measuredKwh, measuredDays, projectedDays and tariffPerKwh (units, currency, whether projection multiplies days by daily average) are completely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Recorded model DustMagnet™ 5210i" is a label, not a verb-plus-resource statement; it never says the tool projects energy/cost from a measured period. The only functional hint is the trailing sentence about the estimate's assumption. The model number (5210i) also conflicts with the tool name (5240i), leaving the target object ambiguous.

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 parameter guidance for one field, not when-to-use guidance. Nothing says when to pick this tool over the many sibling Blueair model tools or over tds_quote_climate_control. No prerequisites, 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.