Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Nanoleaf Solar Garden Lights

tds_purchase_m_nanoleaf_nanoleaf_solar_garden_lights
Read-onlyIdempotent

Recorded model Solar Garden Lights. 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_solar_garden_lights"
  }
}

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?

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description mainly adds that the estimate is model-specific and based on measured/documentation power plus local tariff. It does not describe the returned cost estimate, units, or whether the calculation is annual, leaving some behavioral context unstated.

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?

The definition is only three short sentences and contains no filler. The opening fragment is slightly awkward, but the input-sourcing and estimation basis are front-loaded and easy to scan.

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?

For a five-parameter cost estimator with no output schema and no parameter descriptions, the definition is incomplete: it omits what the result represents and leaves hoursPerDay/daysPerYear and unit conventions unexplained. It gives useful estimation context but not enough to invoke the tool confidently.

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?

With 0% schema description coverage, the description adds sourcing for offeredModel ('seller’s model field or exact variant name'), powerWatts ('measured power or documentation'), and tariffPerKwh ('local electricity tariff'). However, it says nothing about hoursPerDay or daysPerYear, and it does not clarify units such as power W vs kW or tariff currency, so two required parameters remain underexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The title and final sentence make clear this estimates lighting electricity cost for the Nanoleaf Solar Garden Lights, and the model/variant instruction scopes it to that product. The description itself opens with a fragment ('Recorded model...') rather than a verb+resource statement, and it does not explicitly differentiate from sibling product estimators.

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?

It tells the agent where to source values (seller's model field/exact variant, measured power or documentation, local tariff), but never states when this estimator should be used instead of another tool or any preconditions. Guidance is limited to input sourcing rather than tool selection.

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.