Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Nanoleaf Smart Rope Light

tds_purchase_m_nanoleaf_nanoleaf_rope_light
Read-onlyIdempotent

Recorded model Smart Rope Light. 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_rope_light"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 fully covered without description help. The description adds the meaningful point that this is a derived estimate built from external measurements/documentation and a local tariff, implying results are approximation-dependent rather than authoritative. It does not describe the shape of the returned estimate or any caveats about accuracy.

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?

Three short sentences with no filler, and the sourcing guidance is placed before the estimation instruction. The opening fragment 'Recorded model Smart Rope Light.' is a little cryptic and reads like a leftover catalog label, but the text is otherwise 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?

This is a five-required-parameter computation with no output schema and no schema descriptions, so the description is the only place an agent can learn how to fill the fields. It leaves the usage-assumption parameters (hoursPerDay, daysPerYear) undefined and does not state what the returned estimate looks like, which is a substantial gap for a cost-calculation tool.

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 all parameter meaning. It gives context for offeredModel, powerWatts and tariffPerKwh, but says nothing about hoursPerDay or daysPerYear, which are the assumptions that most change the result, nor does it state the currency/unit basis for tariffPerKwh. Two of five required parameters remain completely uninterpreted.

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 names a specific action ('Estimate') and the inputs that feed it ('measured power', 'documentation', 'your local electricity tariff'), and the title pins the resource as electricity cost for the Smart Rope Light. It is distinguishable from the many sibling product-page tools, though the word 'cost' itself appears only in the title, not the body text.

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?

It tells the agent where to source values ('the seller's model field or exact variant name', 'measured power or the exact variant's documentation', 'your local electricity tariff'), which is useful input guidance. But there is no explicit statement of when to call this versus a plain product-lookup sibling, and no exclusions or preconditions.

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.