Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Nanoleaf Shapes

tds_purchase_m_nanoleaf_nanoleaf_shapes
Read-onlyIdempotent

Recorded model Shapes. 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_shapes"
  }
}

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds only the sourcing rule (measured power or variant documentation plus local tariff), which is useful context for a pure-calculation tool but does not describe accuracy caveats, rounding, or how the estimate is derived.

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 filler, so it is compact. However, the lead sentence ("Recorded model Shapes") is neither front-loaded with the action nor informative, and the ordering puts a data-provenance note ahead of the actual estimation logic.

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?

With no output schema and 0% parameter coverage, the description is the only explanatory layer, and it leaves the agent guessing about two of five required inputs and about the shape of the result. For a five-argument estimation tool it should at minimum define the time-basis parameters and state that a cost figure is returned.

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 parameters, so the description must compensate and largely does not. It touches powerWatts ("measured power"), tariffPerKwh ("local electricity tariff"), and offeredModel ("seller's model field or exact variant name"), but hoursPerDay and daysPerYear — the two parameters most likely to be mis-entered — get no mention at all.

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" plus the title's "lighting electricity cost · Nanoleaf Shapes" gives a workable sense of purpose, and the sibling set (all product tools) makes the differentiation plausible. But the description body opens with the cryptic fragment "Recorded model Shapes," which reads as a data-field note rather than a statement of what the tool does, and the body never actually says the output is a cost figure.

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 and your local electricity tariff" tell the agent where to source inputs, which is real guidance. There is no explicit when-to-use versus when-not, and no statement about what to do if measured power is unavailable.

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.