Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Blueair Blue Pure 211i Max

tds_purchase_m_blueair_blue_pure_211i_max
Read-onlyIdempotent

Recorded model Blue Pure 211i Max. 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_211i_max"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds a real modeling caveat — the estimate inherits the use pattern and conditions of the measured period — which is useful and not in structured fields. It still says nothing about units, rounding, or how the projection is computed from tariff.

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?

Three short sentences with no filler, and the model identification leads. The first sentence is close to a restatement of the name/title, but the remaining two each contribute distinct information.

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?

For a five-parameter, fully-required computation with no output schema and no parameter documentation, the description is far too thin. An agent cannot tell what the return value represents (projected kWh over projectedDays?), what tariff unit is expected, or how the two measurement windows interact.

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 must carry the load. It only clarifies offeredModel (seller's model field or exact variant name) and loosely gestures at measured-vs-projected windows; measuredKwh, measuredDays, projectedDays, and tariffPerKwh — including units and currency — remain entirely undefined.

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?

"Recorded model Blue Pure 211i Max" plus "The estimate assumes..." implies a per-model energy projection, and naming the exact model does separate it from the other Blueair variants in the sibling list. But the tool never states its verb or its output (e.g., projected kWh), so the purpose has to be inferred from the title rather than read from 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 input-format guidance for one parameter, not when-to-use guidance. Nothing says when this projection is appropriate versus a quote or a generic climate-control 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.