Skip to main content
Glama

The Doll Scout Home Tools

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

tds_purchase_m_blueair_dustmagnet_5200_series
Read-onlyIdempotent

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

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 does add one useful behavioral caveat: the estimate is only valid if projected use matches the measured conditions. It says nothing about how the projection is computed or what happens with edge inputs (zero measured days, zero tariff).

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 wasted prose, but the first sentence is a near-tautological fragment ('Recorded model DustMagnet™ 5240i') that duplicates the title and is not front-loaded with the tool's actual action. The genuinely useful content is buried in the last sentence.

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 computational tool with no output schema, so the description should explain what the estimate returns (energy over projected days, cost derived from tariffPerKwh). It never states the return value, units, or formula, and four of five inputs are undocumented — significant gaps for an agent trying to call it correctly.

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%, so the description must carry the burden for five required parameters. It gives real guidance for offeredModel ('seller's model field or exact variant name') and weakly gestures at measuredDays/projectedDays via 'your measured period,' but measuredKwh and tariffPerKwh — including units and how tariff is applied — are left completely unexplained.

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 opens with the fragment 'Recorded model DustMagnet™ 5240i,' which restates the tool name/title rather than stating what the tool does. Only the trailing clause ('The estimate assumes the same use and conditions as your measured period') hints that the tool projects energy usage, and that purpose is really carried by the title 'Project measured climate-device energy.' An agent would have to infer the projection verb from the title rather than the description.

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 a parameter value, not about when to invoke this tool. There is no statement of when to use this model-specific projection versus the many sibling model tools or the quote tool, and no prerequisites or exclusions are given.

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.