Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Blueair DustMagnet™ 5440i

tds_purchase_m_blueair_dustmagnet_5400_series
Read-onlyIdempotent

Recorded model DustMagnet™ 5440i. 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_dustmagnet_5400_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already establish that this is a safe, idempotent, non-destructive read operation, so the description does not need to repeat those traits. It adds one meaningful behavioral caveat about projection validity, but it does not explain the calculation basis, how tariff is applied, or what the result 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?

The description is short and free of filler, but it is poorly front-loaded: the first sentence states the model rather than the tool's action. The useful assumption appears at the end, after less important details.

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 calculation tool with no schema descriptions and no output schema, the description is far too thin. It does not explain the projection model, parameter meanings, units, output, or error conditions, leaving an agent unable to invoke it confidently.

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% for five required parameters, and the description only clarifies offeredModel. It does not explain measuredKwh, measuredDays, projectedDays, or tariffPerKwh, nor does it specify units or how the measured period maps to the projection.

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 it never states the actual operation, such as projecting energy use or cost from measured consumption. The title supplies the purpose, but the description itself remains vague and does not clearly distinguish the tool from its model-specific siblings.

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?

It gives a useful input condition ('Use the seller’s model field or exact variant name') and a validity caveat ('assumes the same use and conditions as your measured period'). However, it does not explicitly say when to choose this tool over sibling model tools or when not to use it.

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.