Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · LIFX SuperColor 80" Lightstrip Kit - 1400 Lumens

tds_purchase_m_lifx_lightstrip_80_kit
Read-onlyIdempotent

Recorded model SuperColor 80" Lightstrip Kit - 1400 Lumens. 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_lifx_lightstrip_80_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and a closed-world scope, so the safety profile is covered. The description adds the useful behavioral note that the estimate should be based on measured power or the variant's documentation plus a local tariff, implying a pure local calculation with no live pricing lookup, but it never states units, currency, or what the computed result represents.

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?

It is short with no filler, but it is not front-loaded: the leading sentence about the recorded model is the least actionable part, and the actual estimation instruction arrives last. Missing units mean the brevity comes at the cost of precision rather than being efficient.

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 output schema, zero schema coverage, and no annotations about return values, the description should pin down units, the meaning of the computed figure, and the role of daysPerYear. None of that is present, so an agent can call it but cannot verify it will produce a correctly scaled cost estimate.

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 carry the load and does not. It gestures at 'power' and 'local electricity tariff' and at the model field, but never explains hoursPerDay, daysPerYear, or the units for powerWatts (W vs kW) and tariffPerKwh (currency per kWh), leaving three of five parameters and all units 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 verb 'Estimate' appears only in the second sentence, and the resource is never named directly — the phrase 'electricity tariff' is the only hint that this computes an energy-cost figure. The opening fragment 'Recorded model SuperColor 80" Lightstrip Kit' describes an identity record rather than an action, so an agent must read the whole text plus the title to understand what the tool does.

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 an input-sourcing rule for one parameter, not when-to-use guidance. There is no statement about when to pick this variant tool over the many sibling product tools, nor any exclusion or prerequisite.

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.