Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Coway Airmega Aim

tds_purchase_m_coway_airmega_aim
Read-onlyIdempotent

Recorded model Airmega Aim. 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_aim"
  }
}

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 and destructiveHint=false, so the safety profile is covered and the bar is lower. The description adds real value by disclosing the estimation assumption (projection inherits the use pattern of the measured period), but it says nothing about units, currency, or what the returned estimate looks like for a tool with 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 no filler, but the opening "Recorded model Airmega Aim." is a sentence fragment that spends space on a model name already in the title, while the operation itself is never front-loaded. It is brief without being well-structured.

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 inputs, no output schema, and no parameter descriptions, the definition should explain what is computed and returned (projected kWh and/or cost) and the unit/currency conventions. It covers only the estimation assumption, leaving an agent unable to predict the result or fill tariffPerKwh confidently.

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 must carry the load. It only clarifies offeredModel (seller's model field or exact variant name) and gestures at measured vs projected periods; measuredKwh, tariffPerKwh (which currency?), and projectedDays receive no explanation, and the 366-day cap and bounds are left entirely to the schema.

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 text itself only says "Recorded model Airmega Aim" plus a caveat about the estimate matching the measured period; the actual verb (project energy use/cost for a specific model) lives in the title, not the body. An agent can infer it is a projection over measured data, but the body never states the operation, and with ~30 model-specific siblings differing only by device it gives no signal for why this one is picked beyond the model name.

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 a parameter-selection hint, and the assumption about matching use/conditions is interpretation guidance, but there is no when-to-use vs when-not-to-use framing and no mention of alternatives such as tds_quote_climate_control. Nothing tells the agent the precondition that the measured period must already exist.

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.