Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Nanoleaf Blocks

tds_purchase_m_nanoleaf_nanoleaf_blocks
Read-onlyIdempotent

Recorded model Blocks. 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_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description does add useful context: the estimate is derived from user-supplied measured power or the variant's published data plus a local tariff, implying the result is a computed estimate rather than a lookup. It says nothing about the returned values (cost, currency, period) or assumptions, which matters for a calculation 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?

The description is short and the tariff/power inputs are stated compactly, but it opens with the cryptic fragment "Recorded model Blocks." rather than the purpose, so the most important information is not front-loaded. Length is appropriate; clarity of the opening is not.

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?

A five-parameter, all-required calculation tool with no schema descriptions and no output schema needs the description to explain the usage-rate inputs (hoursPerDay, daysPerYear) and what the result represents. Neither is addressed, so an agent cannot fully determine how to call it or interpret the answer from this definition alone.

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% for all five required parameters, so the description must carry the burden. It clarifies offeredModel (seller's model field or exact variant name), powerWatts ("measured power") and tariffPerKwh ("your local electricity tariff"), but hoursPerDay and daysPerYear — both required, bounded fields — receive no mention whatsoever, leaving an ambiguous pair of inputs undocumented anywhere.

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" appears, but the resource is only implied ("from measured power ... and your local electricity tariff"); the actual purpose — computing an electricity-cost estimate for a Nanoleaf Blocks lighting product — comes mostly from the title. The opening fragment "Recorded model Blocks." does not state an action at all, so an agent must reconstruct intent from the title and schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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" is guidance about how to populate offeredModel, not about when to call this tool versus the many sibling Nanoleaf product tools. There is no when-to-use/when-not condition and no mention of alternatives or prerequisites.

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.