Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Nanoleaf Shapes Expansion Packs

tds_purchase_m_nanoleaf_nanoleaf_shapes_expansion_packs
Read-onlyIdempotent

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

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the agent knows this is a safe, deterministic computation. The description adds the useful behavioral context that values come from measured power or vendor documentation rather than a live lookup, but it never says what the computation returns or in what unit, which matters given there is no output schema.

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, but the opening "Recorded model Shapes Expansion Packs." is a fragment that front-loads a label instead of the action, and the input-sourcing instructions are packed into one long sentence. It is compact without being well-structured.

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 zero schema descriptions and no output schema, so the description carries most of the burden. It leaves the two temporal parameters undefined, does not state the output (currency amount? kWh? annual vs. daily cost), and does not note bounding constraints such as the 24-hour and 366-day maxima, leaving an agent to guess at call shape and result interpretation.

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 all five parameters rely on their names alone. The description adds meaning for offeredModel (seller's model field or exact variant name), powerWatts (measured power or documentation) and tariffPerKwh (local electricity tariff), but hoursPerDay and daysPerYear are left completely unaddressed, including their expected units and typical values.

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?

"Recorded model Shapes Expansion Packs" plus the title's "Estimate lighting electricity cost" convey that this computes an energy-cost estimate for this specific product line, and the product line is distinguishable from the Elements/Lines siblings. However, the description never states the verb+outcome directly in one place ("estimate what, returning what"), so an agent must stitch the title and body together to know what it produces.

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 gives real input-sourcing guidance: use the seller's model field or exact variant name, and derive power from measurements or the variant's documentation plus a local tariff. There is no statement of when to prefer this tool over the sibling expansion-pack tools or what to do when documentation is unavailable, so usage is implied but not disambiguated.

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.