Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Tapo L930-5 Smart Wi-Fi Light Strip

tds_purchase_b05
Read-onlyIdempotent

Recorded model L930-5. 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_b05"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful context about using measured or documented power and a local tariff, but it does not disclose the output format, units, formula, assumptions, or how model mismatches are handled.

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 description is very short and contains no padding. However, "Recorded model L930-5" is cryptic and the estimation action is not front-loaded, which slightly weakens the structure.

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-required-parameter estimator with no output schema and no schema descriptions, the definition is thin. It does not state what is returned, whether the cost is annual or monthly, what currency/units apply, or what formula or rounding is used, so important context must be inferred.

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 the description must carry parameter meaning; it explains offeredModel (seller's model field or exact variant name), powerWatts (measured power or documentation), and tariffPerKwh (local tariff). It says nothing about hoursPerDay or daysPerYear beyond their self-descriptive names, and gives no units or format guidance.

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 title names the purpose (estimate lighting electricity cost for the Tapo L930-5), but the description itself only says "Recorded model L930-5" and "Estimate from measured power...", without explicitly stating that it returns an electricity-cost estimate for that model. It is distinguishable from the purchase-oriented siblings, but the description alone is vague about the resource being estimated.

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?

The description gives input-sourcing guidance such as using the seller's model field or exact variant name and measuring power or using variant documentation plus a local tariff. However, it provides no explicit when-to-use guidance, no exclusions, and no comparison to alternative tools; the agent must infer that this is the estimator to use for this 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.