Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Nanoleaf Elements Expansion Packs

tds_purchase_m_nanoleaf_nanoleaf_elements_expansion_packs
Read-onlyIdempotent

Recorded model Elements Expansion Packs. 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_expansion_packs"
  }
}

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 prose. The description adds real value by framing this as an estimate derived from measured power or manufacturer documentation plus a local tariff, i.e. a pure computation with no side effects. It stops short of describing the returned result or any accuracy/caveat behavior.

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, front-loaded with the product, then input sourcing, then data provenance. The only dead weight is the opening fragment "Recorded model Elements Expansion Packs," which adds nothing beyond the name. Otherwise every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 tool with no output schema and no parameter descriptions, so the description should be carrying more weight than it does. It explains input provenance well but never says what comes back (estimated kWh, cost per day/year) or that the result is an estimate rather than a billed figure. Adequate to call correctly, not complete.

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 carries the burden, and it does clarify three of five parameters: offeredModel (seller's model field or exact variant name), powerWatts (measured power or the variant's documented figure), and tariffPerKwh (local electricity tariff). hoursPerDay and daysPerYear are never mentioned, leaving two required parameters explained only by their self-evident names. Partial compensation, not full.

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 title supplies the actual verb+outcome ("Estimate lighting electricity cost") and the description pins the resource to "Elements Expansion Packs," but the opening sentence "Recorded model Elements Expansion Packs" is a near-restatement of the tool name rather than a purpose statement. An agent can infer this computes electricity cost for that specific product family, but it must read the title to do so. Sibling differentiation is only implicit via the product name.

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 clear input-sourcing guidance, and "Estimate from measured power or the exact variant's documentation and your local electricity tariff" tells the agent where the numbers should come from. However, there is no when-to-use vs. when-not guidance, no mention of prerequisites, and no routing to any alternative tool.

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.