Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Coway Airmega 400

tds_purchase_m_coway_airmega_400
Read-onlyIdempotent

Recorded model Airmega 400. 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_400"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, closed-world, non-destructive operation. The description adds a useful behavioral assumption that the estimate applies only if use and conditions match the measured period, but it says little about calculation, units, limits, or returned result.

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?

The description is short and each sentence carries some utility, especially the exact model-name instruction and the assumption about measured conditions. It is not fully front-loaded because the first sentence is somewhat ambiguous and does not clearly state the tool’s action.

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?

For a five-required-parameter estimation tool with no output schema and no schema descriptions, the description is too sparse. It does not explain how the parameters combine into an estimate, what the output represents, or the meaning of the measured and projected day fields.

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 compensate for all five parameters. It only explains offeredModel by pointing to the seller’s model field or exact variant name; measuredKwh, measuredDays, projectedDays, and tariffPerKwh are not clarified beyond their 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 identifies the specific product variant (Airmega 400) and implies an energy estimate from measured conditions, but it does not plainly state the operation, such as projecting energy use from measured kWh/days. It is distinguishable from sibling model variants by model name, but the core action remains implicit.

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?

It gives a selection hint for the offeredModel field: use the seller’s model field or exact variant name. That helps choose the correct model-specific tool, but there is no explicit when-to-use/when-not-to-use guidance or comparison to alternatives.

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.