Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Nanoleaf Lines Expansion Packs

tds_purchase_m_nanoleaf_nanoleaf_lines_expansion_packs
Read-onlyIdempotent

Recorded model Lines 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_lines_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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered and consistent with an estimation tool. The description adds that figures should come from measured power or the variant's documentation plus a local tariff, which is genuine behavioral context, but it says nothing about the result (a cost figure, an assumption list, or an error when the model is unknown).

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 bloat, but the lead sentence ("Recorded model Lines Expansion Packs") consumes the highest-value position without conveying actionable information. The substantive guidance is pushed into the tail rather than front-loaded.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only estimation tool with a small flat schema and no output schema, the definition is nearly sufficient: an agent knows to supply a model identifier, a wattage, usage hours/days, and a tariff, and to derive the wattage from measurement or documentation. The remaining gap is that two required parameters and the nature of the returned estimate are left implicit.

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% across five required parameters, so the description carries the burden and only partially meets it: it clarifies that offeredModel expects the seller's model field or exact variant name, that powerWatts should be measured or documented, and that tariffPerKwh is the local electricity tariff. hoursPerDay and daysPerYear are never mentioned, and no units or plausibility ranges are given for any parameter.

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 first sentence, "Recorded model Lines Expansion Packs," restates the product name rather than stating an action; the actual verb surfaces only indirectly in "Estimate from measured power ... and your local electricity tariff." An agent can infer this computes an electricity-cost estimate for this specific Nanoleaf Lines Expansion Pack SKU, but it must piece that together from the title plus a subordinate clause rather than from a direct statement.

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" and "Estimate from measured power or the exact variant's documentation and your local electricity tariff" give input-sourcing guidance, which implies the usage context. However, there is no explicit when-to-use or when-not-to-use framing, and no indication of how this differs from the many sibling product tools beyond the SKU itself.

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.