Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Nanoleaf Elements

tds_purchase_m_nanoleaf_nanoleaf_elements
Read-onlyIdempotent

Recorded model Elements. 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_nanoleaf_nanoleaf_elements"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds that results are estimates derived either from measured power or from the variant's documentation plus a local tariff — useful context about precision and inputs. It does not say what the response contains (e.g., cost per day/year, currency assumption), leaving a gap for a computation tool.

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?

Two short sentences with no filler, so it is compact, but the structure is choppy and front-loading is weak: the first fragment conveys almost nothing, and the actionable input guidance arrives second. Terseness here shades into under-specification rather than efficiency.

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 computation tool with no output schema and zero schema coverage, the description should explain the two temporal parameters and at least characterize the returned figure. It covers only three of five inputs and says nothing about the result, so an agent cannot fully predict behavior from the definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 parameter meaning, and it only partially does: powerWatts, tariffPerKwh, and offeredModel get explanation ('measured power', 'your local electricity tariff', 'seller's model field'). hoursPerDay and daysPerYear — both required — receive no mention at all, and units/currency conventions remain unstated.

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 implies a cost estimation from power draw and tariff, but never states plainly that the tool returns an electricity-cost estimate for the Nanoleaf Elements product. The opening fragment 'Recorded model Elements.' is opaque and reads more like a catalog note than a purpose statement. The title does the heavy lifting here; the description alone is only vaguely informative.

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 guidance on how to source offeredModel and implies the tool is per-variant. However, there is no statement of when to use this tool versus the many sibling product estimators, nor any prerequisite or exclusion conditions. Usage is implied rather than specified.

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.