Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Blueair Blue Pure 511

tds_purchase_m_blueair_blue_pure_511
Read-onlyIdempotent

Recorded model Blue Pure 511. 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_blue_pure_511"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/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 contributes one genuinely useful behavioral fact: the estimate assumes the same use and conditions as the measured period. It does not disclose units, return shape, or how the projection is computed.

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, which is fine, but the first sentence duplicates the title and burns the front-loaded position on redundant content rather than on what the tool does.

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?

With five required, entirely undocumented parameters, no output schema, and a numeric projection as the result, the description is far too thin. An agent cannot tell what units measuredKwh uses, what projectedDays does, or what comes back.

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% for five required parameters, so the description must carry the explanatory burden. It only clarifies offeredModel (seller's model field / exact variant name) and says nothing about measuredKwh, measuredDays, projectedDays, or tariffPerKwh — the four parameters that determine the arithmetic.

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?

The description opens with "Recorded model Blue Pure 511," which essentially restates the title's product identifier rather than stating an action. Only the trailing clause about the estimate hints that this projects energy use; there is no verb+resource statement like "project kWh for this model."

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 on how to populate a parameter, not when to select this tool over a sibling. There is no statement of when to use it, when not to, or how it relates to the other Blueair model tools listed.

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.