Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Coway Airmega 450

tds_purchase_m_coway_airmega_450
Read-onlyIdempotent

Recorded model Airmega 450. 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_450"
  }
}

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 needs no repeating. The description adds genuinely useful context that the returned estimate inherits the use assumptions of the measured period, but says nothing about units, the projection formula's sensitivity, 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?

Only three short sentences with no padding, but the lead sentence is a fragment that conveys little, and the ordering puts the vague statement before the useful caveat about matching use conditions. Efficient in length, weak in structure.

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?

This is a multi-parameter numeric projection with no output schema, zero schema coverage, and a tariff input whose semantics are entirely undocumented. The description should specify units, what the result represents, and how tariffPerKwh participates, and it does none of these.

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 coverage is 0%, so the description carries the full burden of explaining five required parameters. It clarifies offeredModel (seller's model field or exact variant name) and gestures at the measured/projected period pair, but tariffPerKwh is never mentioned and units (kWh, days, currency per kWh) go unstated — three of five parameters remain semantically dark.

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 names the exact device ("model Airmega 450") and the estimate framing hints at a projection, but it never states the action with a verb+resource — it opens with the fragment "Recorded model Airmega 450." An agent can infer this is a model-specific projection tool partly because of the title, but the description alone leaves the operation vague.

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 how to format the model parameter, not when to choose this tool over any alternative. Nothing tells the agent when to use this projection tool versus the other Airmega models or other quote tools, and there are no exclusions or prerequisites.

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.