Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · SwitchBot RGBICWW Light Bars

tds_purchase_m_switchbot_switchbot_rgbicww_light_bars
Read-onlyIdempotent

Recorded model RGBICWW Light Bars. 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_light_bars"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that estimates come from measured power or vendor documentation, which is modest but real behavioral context; it says nothing about units, rounding, or what the result looks like.

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 little waste, but the first sentence ('Recorded model RGBICWW Light Bars') carries no actionable information and the ordering buries the actual estimating instruction behind it.

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 computation with no output schema and zero schema descriptions, the definition is thin: two of the five inputs are undocumented and unit conventions for power and tariff are unstated, leaving an agent to guess at valid inputs.

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% across five required parameters, so the description must compensate. It touches offeredModel (seller's model field or exact variant name), powerWatts ('measured power') and tariffPerKwh ('your local electricity tariff'), but hoursPerDay and daysPerYear are never mentioned, and no units (watts vs kW, currency, hours) are clarified.

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

Purpose2/5

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

The description opens with 'Recorded model RGBICWW Light Bars', which restates the product name rather than stating a verb and resource. Only indirectly, via 'Estimate from measured power... and your local electricity tariff', can an agent infer this computes an electricity cost; the actual purpose lives in the title, not the description.

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 parameter-input advice, not when-to-use guidance. There is no statement of when this estimation tool applies versus the many sibling product tools, and no prerequisites or exclusions are given.

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.