Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Blueair Protect 7470i

tds_purchase_m_blueair_protect_7400_series
Read-onlyIdempotent

Recorded model Protect 7470i. 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_protect_7400_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 establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one genuine behavioral fact beyond them — that the projection extrapolates by assuming the projected period shares the use and conditions of the measured period — which is a real modeling assumption the agent should convey. It does not say whether anything is persisted or what the estimate returns.

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?

Two short sentences with no filler, front-loaded with the model identity. The phrasing "Recorded model" is slightly cryptic, but the text stays efficient and earns its space.

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

Completeness1/5

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

With five required parameters, zero schema descriptions, and no output schema, the description is far too thin: units, the projection formula, how measuredDays and projectedDays combine, and whether the result is a single number or a breakdown are all unaddressed. An agent could still call it, but only by guessing at parameter meaning and validity beyond the numeric bounds.

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 full load. It clarifies only offeredModel (model field or exact variant name) and hints at the measured/projected relationship; measuredKwh units, measuredDays vs projectedDays distinction, and what tariffPerKwh represents (currency, per-kWh basis) are left entirely 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 identifies the subject ("Recorded model Protect 7470i") and, via the line about the measurement period, implies an energy/cost projection for that variant. But it never uses a verb stating what the tool actually computes or returns — no "calculates projected kWh/cost from a measured period" — so the agent must infer the operation from the title and parameter names. It does distinguish the variant from its many siblings, but not the operation.

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 when-to-use guidance. There is no statement of when this projection tool applies versus the dozens of sibling model variants or versus tds_quote_climate_control, and no 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.