Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Govee Table Lamp 2

tds_purchase_b03
Read-onlyIdempotent

Recorded model Table Lamp 2. 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_b03"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds a modest amount beyond that by saying the power figure may come either from measurement or from the variant's documentation, which hints at data sourcing. It says nothing about the computation performed or the shape of the result.

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?

The text is short and the estimation method is stated reasonably early, so there is little padding. However the leading fragment 'Recorded model Table Lamp 2' is not a sentence and spends the most prominent position on metadata rather than the tool's action.

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?

A five-parameter estimation tool with no output schema needs the description to say what is returned (annual kWh, annual cost, currency, rounding). The description is silent on all of that and on two of the five required inputs, so an agent cannot call it confidently without guessing parameter meaning.

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 burden and it largely does not. It touches offeredModel, powerWatts (only as 'measured power') and tariffPerKwh (only as 'local electricity tariff'), while hoursPerDay and daysPerYear are never mentioned, and no units (watts vs kilowatts, currency of the tariff) are clarified.

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 sentence 'Estimate from measured power or the exact variant's documentation and your local electricity tariff' implies energy-cost estimation and names the inputs, but the tool never states its resource plainly (annual cost? kWh consumption?). The opening fragment 'Recorded model Table Lamp 2' communicates no action, and nothing distinguishes this estimate tool from the many purchase-oriented siblings.

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?

'Use the seller's model field or exact variant name' is guidance about one input value, not about when to select this tool over an alternative. There is no statement of preconditions, no exclusions, and no routing to any sibling estimation or lookup tool.

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.