Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · LIFX Outdoor SuperColor Path Light Round - 800 Lumens

tds_purchase_m_lifx_path_lights_round
Read-onlyIdempotent

Recorded model Outdoor SuperColor Path Light Round - 800 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_path_lights_round"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 behavior. The description adds useful correctness context about where power and model values should come from, but it does not disclose return units, whether defaults are assumed for missing values, or how out-of-range inputs are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with little waste, and the most important constraint (exact model/variant) is front-loaded. The purpose could be stated more directly instead of beginning with 'Recorded model,' but overall it is tight.

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 estimation tool with no output schema and no schema descriptions, the definition is too thin. It omits units, omits two of the five parameters entirely, and does not say what the estimate returns or what assumptions it uses.

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 must carry the burden. It only touches offeredModel, powerWatts, and tariffPerKwh, and gives no units (W vs kW, currency per kWh), while hoursPerDay and daysPerYear are entirely unexplained.

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 description names the exact model and says to 'estimate from measured power ... and your local electricity tariff,' which implies an electricity-cost calculation. But it never states the verb+resource explicitly as 'estimate electricity cost'; the first two sentences are data-provenance notes rather than a purpose statement, leaving the agent to infer the operation from the title.

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?

The only guidance is on input provenance: use the seller's model field or exact variant name, and estimate from measured power or the variant's documentation. There is no when-to-use guidance, no exclusion for other models, and no mention of when another sibling tool would be appropriate.

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.