Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Coway Airmega 350

tds_purchase_m_coway_airmega_350
Read-onlyIdempotent

Recorded model Airmega 350. 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_350"
  }
}

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 establish the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description does add real context beyond them: the result is an estimate that assumes the same use and conditions as the measured period, which warns the agent that output is a projection, not a measurement. It still says nothing about what the estimate looks like or how the tariff is 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?

Three short sentences with no padding, and the model-identification guidance is front-loaded. However, the opening sentence largely restates the tool name and title, spending its most prominent slot on information the agent already has.

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 mandatory numeric inputs, zero schema descriptions, and no output schema, the description should explain units and what the projection returns. It leaves the agent without enough to populate measuredKwh/tariffPerKwh correctly or to know the shape of the result, which is a real gap for a computational tool.

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. It clarifies only offeredModel (seller's model field or exact variant name) and gestures at the measured-period concept; measuredKwh, measuredDays, projectedDays, and especially tariffPerKwh (units/currency) get no explanation, and the relationship between the two day-count parameters is left ambiguous.

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 350" is a fragment, not a verb+resource statement; the actual action (projecting energy use/cost from a measured period) is only inferable from the title and the parameter names. The model name does distinguish it from the many sibling Airmega variants, but the description itself never says what it computes or returns.

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 guidance about a single parameter value, not about when to choose this tool over another. There is no mention of when-not-to-use, prerequisites, or how to pick among the many sibling model tools, leaving the agent to infer that this is the Airmega-350-specific entry.

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.