Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Blueair Classic 405

tds_purchase_m_blueair_classic_406
Read-onlyIdempotent

Recorded model Classic 405. 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_classic_406"
  }
}

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 this read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds a genuine behavioral caveat — that the estimate carries over assumptions from the measured period — but says nothing about what the returned figure represents (energy versus cost), its units, or how the inputs are combined.

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?

The description is short and front-loaded, but the opening sentence duplicates the title's model identification rather than doing useful work. The remaining two sentences are efficient, though the ordering puts redundant identification ahead of the input guidance.

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-required-parameter computation tool with no output schema and no parameter descriptions, so the description should explain the projection logic and units. Instead it leaves the formula, the role of tariffPerKwh, and the measurement scaling implicit — an agent could invoke it with the right field names but would not understand what the numbers mean.

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 all five required parameters. It clarifies offeredModel (seller's model field or exact variant name) and gestures at the measured-versus-projected relationship, but tariffPerKwh is never mentioned, units for measuredKwh are unstated, and the meaning of measuredDays versus projectedDays is left to inference.

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 Classic 405" restates the model name already in the title and never supplies a verb describing the operation. The phrase "The estimate assumes..." hints that the tool produces an estimate, but the description never says it computes projected energy use or cost from a measured period, so the agent must infer the purpose from the title and parameter names.

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-format guidance for one parameter, not guidance on when to select this tool over siblings such as the Classic 607 or Blue Pure variants. There is no statement of when this projection tool applies versus any alternative, and no prerequisites or 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.