Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · SwitchBot RGBICWW Ceiling Light 12inch

tds_purchase_m_switchbot_switchbot_rgbicww_ceiling_light
Read-onlyIdempotent

Recorded model RGBICWW Ceiling Light 12inch. Use the seller’s model field or exact variant name. Estimate from measured power or the exact variant’s documentation and your local electricity tariff.

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>",
      "powerWatts": "<powerWatts>",
      "hoursPerDay": "<hoursPerDay>",
      "daysPerYear": "<daysPerYear>",
      "tariffPerKwh": "<tariffPerKwh>"
    },
    "name": "tds_purchase_m_switchbot_switchbot_rgbicww_ceiling_light"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: the result is an estimate derived either from measured power or from vendor documentation plus a local tariff, i.e. it is a computation, not a recorded fact. It does not disclose units, output shape, or whether the estimate is annualized.

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?

Two short sentences with no filler, and the product identity is front-loaded before the estimation instruction. Slightly wasteful in that the first sentence restates the product from the title rather than stating the operation.

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 parameter descriptions and no output schema, the description is thin: it leaves the time basis (per day vs per year), unit assumptions for power and tariff, and the form of the returned cost estimate unstated. An agent could plausibly pass mismatched units and get a silently wrong result.

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 carries the full burden. It hints at offeredModel ('seller’s model field or exact variant name'), powerWatts ('measured power') and tariffPerKwh ('local electricity tariff'), but says nothing about hoursPerDay or daysPerYear beyond their names, and never states units or currency conventions for any of the five required parameters.

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 'Recorded model RGBICWW Ceiling Light 12inch' and only implies the actual operation via 'Estimate from measured power... and your local electricity tariff' — the 'electricity cost estimate' framing lives in the title, not the description. The verb is vague ('Estimate' of what?) and nothing distinguishes this energy-cost calculator from the many sibling purchase/catalog tools for other SwitchBot and lighting products.

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 a parameter-format instruction, not a when-to-use rule. The description never says when an agent should call this estimator, what precondition it assumes (a known product model, a measured wattage), or how it relates to the sibling purchase tools.

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.