Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Coway Airmega 100

tds_purchase_m_coway_airmega_100
Read-onlyIdempotent

Recorded model Airmega 100. 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_100"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral caveat beyond that: the estimate assumes the same use pattern and conditions as the measured period, which tells the agent about validity limits of the projection. It does not address units, precision, or how tariff cost is derived.

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, so length is fine, but the opening sentence largely restates the model name already present in the title and tool name, earning little. The most valuable content — the assumption caveat — is placed last rather than front-loaded.

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 computation tool taking five required numeric/string inputs with zero schema descriptions and no output schema, the description is too thin: it omits the expected units for measuredKwh and tariffPerKwh, the relationship between measured and projected days, and what the returned estimate represents. An agent could call it but would be guessing on several inputs.

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 only clarifies offeredModel (seller's model field or exact variant name) and vaguely gestures at measuredDays/measuredKwh via 'measured period.' tariffPerKwh and projectedDays are never explained — no units, currency, or kWh/day semantics.

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 never states a clear action verb; 'Recorded model Airmega 100' identifies the subject (a specific air purifier variant) but leaves the operation to be inferred. Only the phrase 'The estimate assumes...' hints that this produces a projection from measured usage. It does differentiate from siblings implicitly by naming the exact model, but the purpose is 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?

'Use the seller's model field or exact variant name' is input-format guidance for the offeredModel parameter, not guidance on when to choose this tool versus another Airmega variant or versus tds_quote_climate_control. There is no statement of prerequisites, when-not-to-use conditions, or what happens with mismatched model names.

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.