Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Coway Airmega 150

tds_purchase_m_coway_airmega_150
Read-onlyIdempotent

Recorded model Airmega 150. 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_150"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact the annotations cannot convey: the estimate is only valid under the same usage conditions as the measured period. It says nothing about units, whether the result is kWh or currency, or precision, and there is no output schema to fill that gap.

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?

Three short sentences with no padding, and the model identifier is front-loaded. The opening fragment is terse to the point of under-specification, but nothing in the text is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, no-output-schema projection tool, the definition is too thin: an agent cannot know from the description what the return value is (kWh saved, cost, both) or what tariffPerKwh expects. Combined with 0% schema coverage and no output schema, essential calling information is missing.

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 and mostly does not. It adds meaning for offeredModel (seller's model field or exact variant name) and implicitly frames the measured-vs-projected distinction, but tariffPerKwh — a required, bounded numeric input — is never mentioned, nor are units for measuredKwh or the role of measuredDays versus projectedDays.

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?

"Recorded model Airmega 150" identifies the resource variant but is a fragment, not a verb+resource statement of what the tool does. The second half ("The estimate assumes the same use and conditions as your measured period") reveals that the tool produces an energy estimate, but the agent must infer that the tool projects energy/cost from measured kWh. It does at least pin the exact model, which is what distinguishes it from the Airmega 100/160/250 siblings.

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?

"Use the seller's model field or exact variant name" gives practical guidance on selecting this variant over its near-identical siblings. However, it never states when this projection tool should be chosen instead of a sibling or an alternative such as tds_quote_climate_control, and it gives no prerequisites or exclusions.

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.