Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · LIFX Outdoor SuperColor Spot Light - 1600 Lumens

tds_purchase_m_lifx_spot_lights
Read-onlyIdempotent

Recorded model Outdoor SuperColor Spot Light - 1600 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_spot_lights"
  }
}

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, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the estimate is derived either from measured power or from manufacturer documentation combined with a local tariff, which is useful method context. It still does not disclose the output form (kWh vs. currency) or any rounding/assumption behavior.

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, reasonably compact, but the opening model-restatement duplicates the title and adds nothing. The core instruction is split awkwardly between sentence two (model field) and sentence three (estimation method) rather than front-loading what is being computed.

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 five-parameter calculation tool with no output schema and no annotation coverage of computational semantics, yet the description never states the result (annual kWh, cost, or both), the units expected for power and tariff, or how hours-per-day and days-per-year combine. For a tool whose value hinges on a formula, that leaves too much for the agent to infer.

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 numeric parameters, so the description must carry the burden. It only loosely touches offeredModel (seller's model field), powerWatts ("measured power"), and tariffPerKwh ("local electricity tariff"); hoursPerDay and daysPerYear are never mentioned, and no units or expected magnitudes 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 is "Estimate" but the object is only implied by the trailing clause about power and tariff; the description never says plainly that it computes electricity consumption or cost. The model identification sentence ("Recorded model Outdoor SuperColor Spot Light - 1600 Lumens") restates the title rather than clarifying the operation. An agent gets the gist from the title but not from the description body alone.

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" gives real input-selection guidance for identifying the product. However, there is no statement of when this estimation tool applies versus other product tools, and no mention of what to do when measured power is unavailable (the "or the exact variant's documentation" clause is the only fallback offered).

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.