Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · LIFX SuperColor 40" Lightstrip Extension - 700 Lumens

tds_purchase_m_lifx_lightstrip_40_extension
Read-onlyIdempotent

Recorded model SuperColor 40" Lightstrip Extension - 700 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_40_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that this is a derived estimate sourced from measured power or manufacturer documentation plus a local tariff, which tells the agent results are computed estimates, not authoritative figures. It does not disclose the output shape or precision of the estimate.

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 sentences with no wasted clauses of consequence, but the leading sentence restates the model name and adds no actionable information. The actionable instruction is placed last rather than front-loaded, which is a structure miss for an agent scanning definitions.

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 5-parameter computation tool with no output schema and no annotation coverage of return behavior. The description never states what the result is (annual cost, daily cost, currency) or how hoursPerDay and daysPerYear factor in, leaving an agent unable to predict the return value before invoking it.

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 5 required parameters, so the description carries the full burden. It only lightly maps 'measured power' to powerWatts and 'local electricity tariff' to tariffPerKwh; hoursPerDay and daysPerYear are never addressed, and no units or expectations (e.g., watts vs kWh, currency) are clarified beyond the parameter names.

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' and the noun 'electricity tariff' only appear in the final sentence, while the opening sentence ('Recorded model SuperColor 40" Lightstrip Extension - 700 Lumens') merely restates the title/model. An agent can infer this is a per-model electricity-cost estimator, but the purpose is buried rather than front-loaded, and nothing distinguishes it from the many sibling per-product tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/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' and 'Estimate from measured power or the exact variant's documentation' give input-sourcing guidance, which implies when the tool applies. However, there is no explicit when-not guidance, no mention of alternatives (e.g., when to prefer a direct measurement vs. a purchase/price tool), and no statement of prerequisites beyond having a tariff.

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.