Skip to main content
Glama

The Doll Scout Home Tools

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

tds_purchase_m_blueair_blue_pure_511i_max
Read-onlyIdempotent

Recorded model Blue Pure 511i 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_511i_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?

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds one useful behavioral caveat—the estimate assumes the same use and conditions as the measured period—but does not explain the calculation, units, or output. With annotations covering safety, this is moderate added value.

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 little waste: model identification, offeredModel guidance, and an assumption caveat. However, the lead sentence front-loads the model rather than the tool's purpose, and the model name is already present in the title and tool name.

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-required-parameter calculation tool with no output schema and no parameter descriptions, the definition is too thin: it omits what is computed, the output units, and how measured and projected days plus tariff are used. The assumption caveat helps, but not enough.

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 coverage is 0%, so the description must carry all parameter meaning; it only addresses offeredModel by saying to use the seller's model field or exact variant name. It does not explain measuredKwh, measuredDays, projectedDays, or tariffPerKwh, their units, or how tariff affects the estimate.

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 names the specific model and refers to an estimate, but never states the operation explicitly—e.g., that it calculates projected energy use or cost from measured kWh and days. The title supplies the verb, but the description itself leaves the action vague, so it only borderline distinguishes this tool from sibling model variants.

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?

The only guidance concerns how to populate offeredModel: use the seller's model field or exact variant name. There is no statement of when to use this tool, prerequisites, or how to choose among sibling model-specific tools. The implied use is when the model matches, but that must be inferred.

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.