Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Coway Airmega 250

tds_purchase_m_coway_airmega_250
Read-onlyIdempotent

Recorded model Airmega 250. 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_250"
  }
}

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 openWorldHint=false, so the safety profile is covered. The description adds genuine value with the modeling caveat that "The estimate assumes the same use and conditions as your measured period," but leaves the computation basis (units, tariff handling, whether projection is linear scaling) undisclosed.

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 padding, which is good, but the brevity comes at the cost of under-specification rather than tightness. The lead sentence is a fragment that does not front-load 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?

A five-parameter calculation tool with no output schema, no annotation-independent explanation of the result, and 0% schema coverage needs far more than three sentences. An agent cannot tell what the returned projection represents (per-period kWh? cost?) or what the assumption statement means operationally.

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 compensate — and it largely does not. It only illuminates offeredModel (accept the seller's model field or exact variant name); measuredKwh, measuredDays, projectedDays, and tariffPerKwh receive no explanation, including the currency/period semantics of the tariff value.

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 opens with the fragment "Recorded model Airmega 250," which names the device but never states the verb or outcome — projecting energy use from measured kWh and days. The title carries the actual purpose, and the only sibling differentiation is the embedded model number (250 vs. 250s/200m etc.), which is inferred rather than explained.

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 advice for one parameter, not when-to-use guidance. There is no statement of when this tool applies versus the other Airmega variants or versus tds_quote_climate_control, and no prerequisite that a 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.