Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Lume Cube Panel Mini Bi-Color LED Panel Light

tds_purchase_m_lume_cube_panel_mini
Read-onlyIdempotent

Recorded model Panel Mini Bi-Color LED Panel Light. 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_panel_mini"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds that the result is an estimate driven by user-supplied power and tariff and variant documentation, but it does not state accuracy limits, currency handling, or return format. With annotations carrying safety, this is moderate added context.

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; the product identifier is front-loaded and the input guidance follows. The phrase 'Recorded model' and the repeated 'exact variant' are minor redundancies but not wasteful. The structure is easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-input estimator with no output schema and zero schema descriptions, the definition covers the three less obvious inputs and relies on annotations for safety. It omits the time inputs and says nothing about the result shape or currency. Completeness is adequate but has clear gaps.

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 coverage is 0%, so the description must carry parameter meaning. It explains offeredModel (seller's model/variant), powerWatts (measured or documented power), and tariffPerKwh (local tariff), but it never mentions hoursPerDay or daysPerYear. Those names are self-explanatory, yet the description still leaves two of five required inputs unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The title and description together identify a specific action (estimate electricity cost) for a specific product (Panel Mini Bi-Color LED Panel Light). The verb 'Estimate' and the resource 'electricity cost' are clear, though the opening 'Recorded model' is slightly opaque. Sibling products are distinguished by model name, not by behavioral comparison.

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?

The description tells the agent to use the seller's model field or exact variant name and to base power on measured values or the variant's documentation plus local tariff. That is input-sourcing guidance, not an explicit when-to-use/when-not statement or comparison to alternatives. Usage is implied rather than fully routed.

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.