Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Levoit Neoclassic 450 Luftbefeuchter

tds_purchase_m_levoit_levoit_neoclassic_450_luftbefeuchter
Read-onlyIdempotent

Recorded model Neoclassic 450 Luftbefeuchter. 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_levoit_levoit_neoclassic_450_luftbefeuchter"
  }
}

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 read-only, idempotent, closed-world behavior, so the safety profile is covered. The description adds genuinely useful scope: the projection inherits the use conditions of the measured period, which tells the agent the result is a conditional extrapolation, not a measured value. It omits units, rounding, and any note on how outliers in the measured period propagate — a moderate gap for a computation tool.

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 lead sentence is wasted on restating the model name while the substantive constraint appears last. Front-loading the assumption and units would make the same word count far more useful.

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-required-parameter calculator with zero schema descriptions and no output schema needs the description to explain inputs, units, and what the projection returns. It supplies only a partial model-name hint and an assumption caveat, leaving tariff semantics and result interpretation undocumented.

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% for all five required parameters, so the description carries the full burden and largely fails. It clarifies offeredModel (seller's model field or exact variant name) and loosely gestures at measuredKwh/measuredDays via "measured period" and at projectedDays via "estimate," but tariffPerKwh is never mentioned, and no units (kWh, days, currency per kWh) or boundary behavior (e.g., 366-day cap) are explained.

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 Neoclassic 450 Luftbefeuchter" mostly restates the tool name and title rather than naming an action; the only functional hint comes from "The estimate assumes the same use and conditions as your measured period," which implies an energy projection but never states the verb or output. An agent can guess this computes projected consumption for that specific humidifier model, but it must infer rather than read it.

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-format guidance for one parameter, not when-to-use guidance. Nothing distinguishes this from the near-identical siblings (Neoclassic 350, 450s, Classic 300s) or from tds_quote_climate_control, so an agent has no stated rule for picking among them.

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.