Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Coway Airmega 250S

tds_purchase_m_coway_airmega_250s
Read-onlyIdempotent

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

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?

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds one meaningful behavioral caveat: the estimate assumes the same use and conditions as the measured period. It still does not describe the calculation, units, or what the response contains.

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?

The description is short, with only three sentences and little wasted wording. However, it is front-loaded with a model identifier rather than the action, and the structure does not prioritize the core projection behavior an agent needs first.

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 five-parameter numeric projection tool with no output schema and no schema descriptions, the definition is substantially incomplete. It omits what is being projected, how measuredDays and projectedDays relate, what tariffPerKwh means, and what result the caller should expect.

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%, with five required parameters and no per-parameter descriptions in the schema. The description only adds meaning for offeredModel by advising use of the seller's model field or exact variant name; measuredKwh, measuredDays, projectedDays, and tariffPerKwh remain unexplained beyond their names and numeric constraints.

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 title indicates projecting measured climate-device energy, and the description identifies the exact model and mentions an estimate. However, the description itself never states the core action clearly, such as computing projected energy or cost from measured usage, so the purpose is only inferable from the title and context.

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 definition gives some guidance for the offeredModel parameter by saying to use the seller's model field or exact variant name, and it notes an assumption about matching use conditions. It does not explain when to use this tool versus alternatives such as tds_quote_climate_control or other model-specific projection tools, nor does it specify 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.