Skip to main content
Glama

The Doll Scout Home Tools

Estimate lighting electricity cost · Lume Cube Studio Panel Edge-Lit LED Panel Light

tds_purchase_m_lume_cube_studio_panel
Read-onlyIdempotent

Recorded model Studio Panel Edge-Lit 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_studio_panel"
  }
}

Input Schema

NameRequiredDescriptionDefault
powerWattsYes
daysPerYearYes
hoursPerDayYes
offeredModelYes
tariffPerKwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful context about estimation sources—measured power, exact variant documentation, and local tariff—but does not disclose assumptions, output format, or that the result is an estimate rather than an actual bill.

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 description is brief and avoids wasted words, but it is not front-loaded with the core action. It opens with 'Recorded model Studio Panel Edge-Lit LED Panel Light' before indicating that the tool estimates cost, making the purpose slower to grasp.

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-required-parameter calculation tool with no output schema, the description provides enough to infer the calculation basis but omits what the returned estimate represents and how hoursPerDay and daysPerYear feed into it. The annotations cover safety, but output semantics and full parameter coverage remain incomplete.

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?

With 0% schema description coverage, the description must carry parameter meaning. It clarifies offeredModel as the seller’s model field or exact variant name, powerWatts as measured power or documented power, and tariffPerKwh as the local electricity tariff, but it leaves hoursPerDay and daysPerYear unexplained beyond their self-descriptive names.

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 says 'Estimate from measured power or the exact variant’s documentation and your local electricity tariff,' which implies a cost calculation, but it never explicitly states that it estimates lighting electricity cost. The object being estimated is only clear from the title and tool name, leaving the purpose somewhat vague.

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?

The description gives input guidance ('Use the seller’s model field or exact variant name') but provides no when-to-use guidance relative to alternatives. It does not say to use this tool for cost estimation rather than product purchase, nor does it exclude any sibling tools.

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.