Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · LIFX Luna SuperColor LED Smart Lamp - 1000 Lumens

tds_purchase_m_lifx_luna
Read-onlyIdempotent

Recorded model Luna SuperColor LED Smart Lamp - 1000 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_luna"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 the important behavioural caveat that the result is an *estimate* derived from measured or documented power plus the caller's own tariff, implying the output is assumption-dependent rather than authoritative. It does not state the output's unit, period, or currency, which is the most-needed behavioural detail for a cost calculator.

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 padding, but the ordering is poor: the lead sentence is a product label rather than the operation, and the input-sourcing guidance is buried after it. The volume is appropriate; the front-loading is not.

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 tool with five required parameters, zero schema description coverage and no output schema, the description should specify what is returned (annual cost, kWh, currency) and define the two usage assumptions. Neither is present, leaving the agent to guess the computation (power x hours x days x tariff) and the result's unit.

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 maps loosely onto two of five parameters (powerWatts via "measured power", tariffPerKwh via "your local electricity tariff") and hints at offeredModel, but hoursPerDay and daysPerYear are never mentioned, and no units, currency, or expected magnitude are given for any parameter.

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 description pairs the resource ("Luna SuperColor LED Smart Lamp - 1000 Lumens") with the action "Estimate" and names the driving inputs (measured power, electricity tariff), so an agent can tell this is a per-model electricity-cost estimator rather than a generic product lookup. It stops short of a crisp single statement of the operation (e.g. "estimate annual cost for this specific model"), and the opening "Recorded model ..." sentence is more catalogue label than purpose statement.

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 guidance on how to source inputs, which is genuinely useful for a product-specific estimator. However, there is no when-to-use / when-not-to-use framing and no signal about how an agent should choose among the many sibling product estimators beyond matching the model name.

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.