Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Blueair Classic 605

tds_purchase_m_blueair_classic_607
Read-onlyIdempotent

Recorded model Classic 605. 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_607"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 adds genuinely useful behavioral context in stating that the projection assumes the same usage and conditions as the measured period, which tells the agent what the estimate means. It does not disclose the return shape or any limits of the calculation.

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 model-matching instruction is easy to find. The first sentence is largely redundant with the title, which is the only waste.

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

Completeness4/5

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

For a five-parameter calculation tool with an empty schema-description layer, no output schema, and dense sibling competition, the definition leaves the input semantics and the returned projection undescribed. The assumption note and model-matching rule help, but an agent would still be guessing at units and output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 (offeredModel, measuredKwh, measuredDays, projectedDays, tariffPerKwh), so the schema supplies only types and bounds, no meaning. The description compensates for only one parameter (offeredModel) and says nothing about units or interpretation for the kWh, day-count, and tariff inputs. This is well under what a 0%-coverage schema requires.

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 never states a verb or operation outright; purpose is only inferable from "The estimate assumes the same use and conditions as your measured period." The opening "Recorded model Classic 605" largely restates the title, so the model identity is conveyed but the action (projecting energy use for this model) is left to inference from the title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/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" gives real selection guidance among the many sibling model variants, which is the main routing risk here. However, there is no explicit when-to-use/when-not guidance, no statement that this tool is specific to the Classic 605 versus the sibling 406 or Pro CP7i, and no prerequisite context beyond the model-matching instruction.

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.