Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Lume Cube Edge Light Go Task Light with Red Light Mode

tds_purchase_m_lume_cube_edge_light_go
Read-onlyIdempotent

Recorded model Edge Light Go Task Light with Red Light Mode. 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_lume_cube_edge_light_go"
  }
}

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 readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds only that this is an 'estimate' derived from measured power and a local tariff, which implies a pure local computation, but says nothing about output shape, rounding, or assumptions.

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?

Three short sentences with no filler, and the variant-scoping rule is front-loaded. The first sentence is close to a restatement of the product name, which costs a little density but also serves to disambiguate the variant.

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 calculation tool with no output schema and zero schema descriptions, the definition should explain how hoursPerDay and daysPerYear combine into the result and what units/format the estimate takes. Two of the five inputs remain unexplained, leaving real ambiguity about the calculation.

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% across five required parameters, so the description must carry the meaning. It clarifies offeredModel (seller's model field or exact variant name), powerWatts (measured power or documented wattage), and tariffPerKwh (your local tariff), but hoursPerDay and daysPerYear — the two parameters that determine the annualized result — get no explanation at all.

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 description identifies the exact product variant ('Edge Light Go Task Light with Red Light Mode'), but the actual action — estimating electricity cost — is carried by the title, not the description text. An agent reading only the description sees model identification and input-sourcing advice, not a clear verb+resource 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?

It gives useful sourcing rules: take the model from the seller's model field or exact variant name, and derive power from measurement or the variant's documentation plus a local tariff. It does not say when to prefer this estimator over any alternative approach, nor what to do when no measured power exists.

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.