Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Nanoleaf 4D Screen Mirror

tds_purchase_m_nanoleaf_nanoleaf_4d
Read-onlyIdempotent

Recorded model 4D Screen Mirror. 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_4d"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 covered. The description adds that the result is a computed estimate derived from measured power or vendor documentation plus a local tariff, which is useful context beyond the annotations. However, with no output schema it never says what the estimate returns (annual cost? currency? per-model total), which is a real behavioral 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?

Short and mostly front-loaded, with no filler sentences. But the lead sentence 'Recorded model 4D Screen Mirror' spends prime space on an ambiguous fragment instead of stating the operation, which weakens structure for an agent skimming the first line.

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?

Five required parameters, zero schema description coverage, and no output schema means the description must explain both input meaning and return value. It does neither fully: it omits units/currency, the meaning of the usage-rate parameters, and what the estimate actually outputs. For a pure-computation tool that is a substantial shortfall.

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%, so the description must carry all parameter meaning. It only clarifies offeredModel (seller model field or exact variant name) and gestures at powerWatts and tariffPerKwh sources; hoursPerDay, daysPerYear, and the currency/unit basis of tariffPerKwh are left entirely to the field names. That is insufficient for a five-required-parameter compute tool.

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?

With the title, the definition reads as a specific verb+resource: estimate electricity cost for the Nanoleaf 4D Screen Mirror from power draw, usage hours and tariff. The description's opening line ('Recorded model 4D Screen Mirror') is a product-record fragment rather than a purpose statement, so the intent is carried mostly by the title plus the second sentence. No sibling differentiation is offered, but the compute-vs-purchase distinction is clear enough from the wording.

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 real guidance on how to source the inputs. What is missing is when to call this tool at all versus the many sibling purchase/listing tools, and any exclusion or precondition (e.g. only for this one model).

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.