Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Philips Hue Go portable accent light

tds_purchase_b01
Read-onlyIdempotent

Recorded model Go 7602031U7. 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_b01"
  }
}

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 read-only, idempotent, closed-world, non-destructive behavior, so safety is covered. The description adds useful provenance guidance (prefer measured power or vendor documentation over guesses), but says nothing about what the result contains or how variants affect the estimate. No contradiction with the annotations.

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 little waste, but the lead sentence is a bare model number ('Recorded model Go 7602031U7') that front-loads a specific SKU instead of the tool's action. Purely informational and slightly misordered for an agent scanning for purpose.

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 with zero schema descriptions and no output schema mean the description carries most of the burden, yet it explains at most three inputs and never describes the returned estimate. For a numeric-estimation tool this leaves meaningful gaps an agent can't resolve from structured fields.

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 compensate. It clarifies only offeredModel (seller's model field or exact variant name) and loosely gestures at powerWatts and tariffPerKwh; hoursPerDay and daysPerYear get no explanation at all, leaving half the required inputs undefined.

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 uses the verb 'Estimate' and ties it to 'measured power ... and your local electricity tariff', which implies an electricity-cost calculation, but it never explicitly names the output (cost/energy per year). The concrete 'what' is left to the title, so intent is inferable rather than stated.

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 input-sourcing guidance ('Use the seller's model field or exact variant name', 'measured power or the exact variant's documentation ... your local electricity tariff'), which steers how to fill values. It gives no guidance on when to use this tool versus any alternative, nor on what to do if the variant can't be matched or power is unknown.

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.