Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Blueair PetAir Pro

tds_purchase_m_blueair_petair
Read-onlyIdempotent

Recorded model PetAir Pro. 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_petair"
  }
}

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, so safety is covered. The description adds real context beyond that: the output is an estimate and it assumes the same use and conditions as the measured period. It still omits how the extrapolation is computed and what the response contains.

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?

Three short sentences with little filler, but the opening 'Recorded model PetAir Pro' duplicates the title and delays the relevant content. The most useful sentence, about the assumption behind the estimate, is last rather than front-loaded.

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 parameter descriptions and no output schema, so the description must carry more weight. It never says what the tool returns (annual kWh, cost, both) or how tariffPerKwh and projectedDays combine, leaving the agent to guess at the result shape.

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, so the full burden falls on the description, and it only clarifies one of them (offeredModel, via 'seller's model field or exact variant name'). measuredKwh, measuredDays, projectedDays, and tariffPerKwh are left entirely to their names, though those names are largely self-explanatory and the description's note about measured-period assumptions indirectly frames the measured/projected split.

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 says 'Recorded model PetAir Pro' and refers to 'The estimate,' which hints at an energy projection but never states a clear verb+resource such as 'projects energy consumption for this air purifier from your measured usage.' The purpose has to be inferred from the title rather than the body text.

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-formatting guidance, not when-to-use guidance. Nothing says when this projection tool should be chosen over the sibling quote tool (tds_quote_climate_control) or over simply reporting measured values, and no 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.