Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · SwitchBot RGBICWW Ceiling Light 15inch

tds_purchase_m_switchbot_switchbot_rgbicww_ceiliing_6fff9ac9
Read-onlyIdempotent

Recorded model RGBICWW Ceiling Light 15inch. 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_ceiliing_6fff9ac9"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish a safe, read-only, idempotent, closed-world operation, so the safety profile is covered. The description does add one meaningful behavioral fact: the output is an estimate derived from measured power or vendor documentation plus a user-supplied tariff, i.e. a computed projection rather than a live price quote. It stops short of disclosing what happens when measured wattage is unknown or how the estimate is derived (e.g. peak vs average draw).

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 opening 'Recorded model RGBICWW Ceiling Light 15inch' merely restates the title/model instead of front-loading the verb 'estimate electricity cost'. The remaining two sentences mix selection guidance with unit-source guidance, so the actionable content is not cleanly ordered.

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?

Five required parameters, no output schema, and no property descriptions mean the definition must explain the full input-to-output contract, and it does not. It omits how hoursPerDay and daysPerYear are expected to be supplied and says nothing about the shape or unit of the returned estimate (annual cost, currency handling), which an agent needs in order to use the result.

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 coverage is 0%, so the description carries the full burden. It does clarify three of the five inputs — offeredModel ('seller’s model field or exact variant name'), powerWatts ('measured power'), and tariffPerKwh ('your local electricity tariff') — which is genuine value over bare names. However, hoursPerDay and daysPerYear, both required with defined ranges, are never mentioned, and the measurement basis for power (rated vs. measured at the wall) is ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The combination of title and description makes clear this computes an electricity-cost estimate for one specific ceiling light variant, and 'Estimate from measured power ... and your local electricity tariff' names the computation rather than a product lookup. The gap: the description never addresses the near-duplicate sibling 'tds_purchase_m_switchbot_switchbot_rgbicww_ceiling_light' (no variant hash), so an agent cannot tell from the text which of the two to pick.

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?

There is no statement of when to use this tool versus the dozens of sibling purchase tools, and no exclusions or prerequisites. The only directional sentence, 'Use the seller’s model field or exact variant name,' is guidance about the offeredModel argument, not about tool selection.

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.