Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · SwitchBot Battery Circulator Fan 2 Pro

tds_purchase_m_switchbot_switchbot_battery_circulat_1022947a
Read-onlyIdempotent

Recorded model Battery Circulator Fan 2 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_switchbot_switchbot_battery_circulat_1022947a"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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, closed-world read (readOnlyHint=true, destructiveHint=false). The description adds one genuinely useful disclosure, that the estimate assumes the same use and conditions as the measured period, but says nothing about the calculation, units, or return shape. That is a modest addition on top of the annotation coverage.

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 no filler, but the structure is poorly front-loaded: the opening fragment names a product rather than the tool's action, and the most useful constraint (the same-conditions assumption) appears last. It is compact but not well organized.

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 projection tool with no output schema and 0% schema coverage, so the description carries the full explanatory burden. It omits what is returned, how the projection is computed, and the meaning of four parameters, so an agent cannot call 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%, so the description must carry the parameter burden, and it does not: only offeredModel gets guidance ("seller's model field or exact variant name"). It never explains measuredKwh units, the distinction between measuredDays and projectedDays, or that tariffPerKwh is a currency rate, leaving four of five required parameters undocumented.

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 opens with the fragment "Recorded model Battery Circulator Fan 2 Pro", which names the product variant but never states the action: that this projects climate-device energy use from measured consumption. Combined with the title, an agent can infer the intent, but the description alone does not give a clear verb+resource and does not explain how this differs from the many sibling per-product entry tools.

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, "Use the seller's model field or exact variant name", concerns input formatting for offeredModel, not when to select this tool. There is no statement of when to use this versus a sibling or a generic quote tool, and no prerequisites are mentioned.

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.