Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Elgato Key Light Neo

tds_purchase_b04
Read-onlyIdempotent

Recorded model Key Light Neo. 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_b04"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/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 covered. Beyond that the description only says to source numbers from measured power or vendor documentation and a local tariff, which is input-provenance advice rather than behavioral disclosure (no mention of accuracy, unit assumptions, rounding, or what the returned figure represents).

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 the least informative part and the informative constraint about sourcing values comes last. Structure is compact yet not front-loaded on the actual 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?

A pure-computation tool with five required numeric/string inputs, no schema descriptions, and no output schema needs the description to at least sketch the computation or the meaning of the result. The description never explains how the inputs combine, what hoursPerDay and daysPerYear represent, or what the estimate is expressed in.

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% for five required parameters, so the description has to compensate. It does add meaning for three of them (offeredModel via seller's model field/variant name, powerWatts via measured power, tariffPerKwh via local tariff), but hoursPerDay and daysPerYear are never mentioned, and no units or value expectations (e.g. hours as decimal, tariff currency) are given.

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 verb 'Estimate' appears, and the resource is only inferable from the title ('lighting electricity cost') and the parameter names. The opening sentence 'Recorded model Key Light Neo' describes a catalog record rather than stating what the tool computes, so an agent must combine title and schema to know this returns an electricity-cost estimate. It is not tautological, but it is vague on its own.

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 how to fill one field, not when to call this tool. There is no statement of when to prefer this over the many sibling lighting-purchase tools, no prerequisites, and no exclusions.

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.