Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Coway Airmega 300

tds_purchase_m_coway_airmega_300
Read-onlyIdempotent

Recorded model Airmega 300. 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_m_coway_airmega_300"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety bar is low. The description does add one genuinely useful caveat beyond annotations — that the estimate inherits the use conditions of the measured period — but says nothing about units, response shape, or what happens for bad measured inputs.

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 bloat, and the model-matching rule is front-loaded. However, the opening sentence spends its one line on a redundant restatement of the model name rather than on what is computed.

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?

With five required numeric/string parameters, no schema descriptions and no output schema, the definition should explain the measurement inputs, the tariff unit, and what the projection returns. It covers only model matching plus one assumption, leaving an agent unable to call it confidently beyond guessing from parameter names.

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%, so the description must carry parameter meaning, yet it only addresses offeredModel (use the seller's model field or exact variant name). measuredKwh, measuredDays, projectedDays and tariffPerKwh (including their currency/unit assumptions) get no explanation at all.

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?

"Recorded model Airmega 300" largely restates the tool name/variant label rather than stating the action. Only the word "estimate" hints that the tool projects energy use for this device model, so an agent must infer the verb from the title or sibling naming pattern.

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" gives some selection guidance among the many Coway Airmega siblings, but it never says when to invoke this projection tool versus alternatives such as tds_quote_climate_control, nor any preconditions on measured data.

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.