Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Govee RGBICW Smart Corner Floor Lamp Basic

tds_purchase_b02
Read-onlyIdempotent

Recorded model RGBICW Smart Corner Floor Lamp Basic. 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_b02"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 covered. The description adds that the result is an estimate derived from measured power or vendor documentation plus a local tariff, which explains the computation's basis. It does not say what the response contains (annual cost, currency, kWh) despite there being no output schema.

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?

Three short sentences with no padding, but the lead sentence is a bare noun phrase ("Recorded model ...") that front-loads metadata instead of the tool's action. The most useful instruction, the estimation basis, arrives last.

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?

With five required parameters, zero schema description coverage and no output schema, the description is the only place an agent could learn the return shape and the meaning of hoursPerDay/daysPerYear, and it supplies neither. It also does not say whether offeredModel is validated against a catalog or accepted as free text, which matters for a 400-character string input.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, and it does meaningful work: it clarifies that offeredModel should be the seller's model field or exact variant name, that powerWatts may be measured or taken from documentation, and that tariffPerKwh is the user's local rate. hoursPerDay and daysPerYear are left unaddressed, though their names and numeric bounds convey units, so this is a modest rather than a serious gap.

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 opens with a model-name fragment ("Recorded model RGBICW Smart Corner Floor Lamp Basic") and then says "Estimate from measured power or the exact variant's documentation and your local electricity tariff." The object of "estimate" is never stated in the description itself — an agent must fall back on the title to learn that the output is an electricity cost. That is a vague purpose rather than a specific verb+resource.

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" give real guidance on where to source inputs, which is more than nothing. However, there is no statement of when this tool applies versus the many sibling tds_purchase_* tools, and no exclusions or prerequisites for invoking it.

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.