Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Nanoleaf Skylight

tds_purchase_m_nanoleaf_nanoleaf_skylight
Read-onlyIdempotent

Recorded model Skylight. 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_skylight"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds almost nothing beyond that: it does not say the result is a computed figure, whether it is per-year cost, what currency basis applies, or that the tool performs no lookup of real market rates and instead relies solely on user-supplied tariff. For a pure calculation tool whose only value is the computation it performs, that is a real gap.

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?

At three short sentences it is efficiently sized with no filler. However, it is not front-loaded: the vague 'Recorded model Skylight' fragment leads, and the actual operation only emerges in the final clause, forcing the agent to read to the end to learn what the tool does.

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?

There is no output schema, so the description carries the return-value burden, yet it never says what comes back (a cost figure, presumably annual, in some currency) or how the inputs combine. For a five-required-parameter numeric calculator with zero schema descriptions, the definition is under-specified in exactly the places an agent needs to fill parameters correctly.

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 carry the full explanatory burden. It gives useful hints for offeredModel (seller's model field or exact variant name), powerWatts (measured power or manufacturer documentation) and tariffPerKwh (local electricity tariff), but says nothing about hoursPerDay or daysPerYear, which drive the multiplication and are the most likely source of user error (e.g. per-day average usage, 365 vs. billing days).

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 operative sentence ('Estimate from measured power or the exact variant's documentation and your local electricity tariff') conveys a cost-estimation operation on the Skylight model, but the opening fragment 'Recorded model Skylight' is ambiguous and the description never states what is being estimated (annual electricity cost) or in what unit. It is distinguishable from siblings only by the model name, not by any stated verb+resource pairing.

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 a data-entry hint for one parameter, not when-to-use guidance. There is no statement of when this tool applies versus the many other purchase-catalog siblings, no prerequisites, and no indication of when to prefer measured power over documentation values.

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.