Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Coway Airmega 200M

tds_purchase_m_coway_airmega_200m
Read-onlyIdempotent

Recorded model Airmega 200M. 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_200m"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/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 scope, so the safety profile is covered. The description adds one real behavioral insight — the estimate's validity depends on the projection period sharing the conditions of the measured period — but says nothing about what is produced or how the model-specific coefficients are applied.

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?

At three short sentences it is not bloated, and the key assumption is placed last. The opening sentence "Recorded model Airmega 200M" is a fragment that spends words restating the tool name without adding actionable information.

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-required-parameter computational tool with no output schema and no schema descriptions, the description is too thin — it never states units (kWh, days, tariff currency), never explains how the measured pair maps to the projected horizon, and never tells the agent what the projection returns.

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%, so the description must carry the full semantic load for five required parameters. It clarifies only offeredModel (seller's model string or exact variant name); measuredKwh, measuredDays, projectedDays, and tariffPerKwh are left completely undefined in terms of units, relationship, or expected magnitude.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Recorded model Airmega 200M" restates the tool name's product variant rather than stating an action. The only functional hint is the word "estimate" in the third sentence, so an agent must infer from the title and parameter names that this projects energy use for the Airmega 200M from measured data.

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" effectively tells the agent this tool is the 200M variant of a per-model family, which routes it away from the 100/150/250 siblings. However, there is no statement of when this tool is inapplicable or of any prerequisite, such as needing a completed measured period first.

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.