Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Coway Airmega 160

tds_purchase_m_coway_airmega_160
Read-onlyIdempotent

Recorded model Airmega 160. 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_160"
  }
}

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, non-destructive, closed-world behavior, so the safety profile is covered. The description contributes a genuinely useful caveat that the estimate inherits the use conditions of the measured period, but says nothing about how the projection is computed, how tariff enters, or what comes back.

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, no padding, but the opening sentence re-states the model name and consumes prime front-loaded space without conveying what the tool does. The one substantive caveat is buried last.

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 computation-style tool with five required numeric inputs, no output schema, and no annotations explaining result semantics needs more than this. Missing: unit conventions, the relationship between measuredDays and projectedDays, and the meaning/form of the returned estimate.

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 offeredModel (seller model field or exact variant name) and implies the measured-vs-projected distinction, but leaves measuredKwh units, projectedDays, and especially tariffPerKwh (currency? per kWh?) 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?

"Recorded model Airmega 160" largely restates the title/model rather than stating the operation. Only the phrase "The estimate assumes the same use and conditions as your measured period" hints that this projects energy use, and the actual behavior (a read-only projection from measured kWh/days to a projected period) must be inferred from the parameter names.

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 only guidance is "Use the seller's model field or exact variant name," which is a formatting instruction for one parameter, not a when-to-use rule. Nothing tells the agent how to choose between this and the many sibling Airmega variants (100, 150, 200m, 250...) or versus tds_quote_climate_control.

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.