Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Eva-Dry E-333 renewable mini dehumidifier

tds_purchase_c23
Read-onlyIdempotent

Recorded model E-333. Use the seller’s model field or exact variant name. The estimate assumes the same use and conditions as your measured period.

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>",
      "measuredKwh": "<measuredKwh>",
      "measuredDays": "<measuredDays>",
      "projectedDays": "<projectedDays>",
      "tariffPerKwh": "<tariffPerKwh>"
    },
    "name": "tds_purchase_c23"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds only the modeling caveat that the estimate inherits the measured period's use and conditions, and says nothing about what the estimate returns (energy, cost, both), units, or rounding — notable since there is 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 little waste, but the lead sentence ('Recorded model E-333') is a hardcoded SKU note of low value that occupies the front-loaded position where the core action should be. The ordering puts a data artifact ahead of 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 five-parameter computation tool with no output schema and no parameter documentation needs the description to explain the formula and units. Instead it supplies one input hint and one assumption, leaving an agent unable to know what the returned value represents.

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

Parameters2/5

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

Schema description coverage is 0% across five required parameters, so the description carries the full burden. It clarifies only offeredModel (seller's model field or exact variant name) and gestures at measured versus projected days, leaving measuredKwh, measuredDays, projectedDays and tariffPerKwh — including units and tariff currency — entirely undefined.

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

Purpose2/5

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

The description never states the action. It opens with 'Recorded model E-333' and only implies an estimate via 'The estimate assumes the same use and conditions as your measured period.' An agent must infer from the title ('Project measured climate-device energy') that this computes a projection; nothing in the text says what is computed from what.

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?

No when-to-use guidance and no routing to any sibling (e.g. tds_quote_climate_control or the per-product purchase tools). The only directional statement, 'Use the seller's model field or exact variant name,' is input hygiene for one parameter rather than a condition for choosing this tool.

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.