Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Blueair Classic Pro CP7i

tds_purchase_m_blueair_classic_pro_cp7i
Read-onlyIdempotent

Recorded model Classic Pro CP7i. 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_pro_cp7i"
  }
}

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety behavior is covered. The description adds one genuine caveat beyond that: the projection assumes the same usage conditions as the measured period, which warns the agent the output is conditional. It stops short of explaining how the estimate is derived, what the return looks like, or whether unknown model names cause failure.

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 padding, and the caveat about shared use conditions is clearly stated. The opening fragment 'Recorded model Classic Pro CP7i' is a weak lead that spends a sentence restating the title rather than stating the action. Otherwise the structure is clean.

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 parameters at 0% schema coverage and no output schema, the description should clarify units (kWh, days, tariff currency), what the returned estimate represents, and how measuredDays interacts with projectedDays. None of that appears, so an agent cannot be confident it is calling this correctly even though the safety profile is fully annotated.

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, yet it only clarifies offeredModel (seller's model field or exact variant name). measuredKwh, measuredDays, projectedDays and tariffPerKwh receive no units, currency, or relationship explanation beyond their names, leaving the measured-vs-projected day semantics ambiguous.

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 specific product variant ('Classic Pro CP7i') and gestures at an estimate via 'The estimate assumes the same use and conditions as your measured period,' so an agent can infer this projects energy use for a given model. However, it never states a verb like 'compute' or 'project' for the measured-to-projected kWh calculation, so the core action stays implicit. It also does not distinguish this from the many sibling per-model tools, since differentiation is entirely by product name.

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 fill offeredModel, not on when to invoke this tool versus alternatives such as tds_quote_climate_control. There is no statement of prerequisites (e.g., that a measured period must already exist) or of when-not-to-use. The agent must infer that tool selection is purely by matching product model.

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.