Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Levoit Neoclassic 350 Luftbefeuchter

tds_purchase_m_levoit_levoit_neoclassic_350_luftbefeuchter
Read-onlyIdempotent

Recorded model Neoclassic 350 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_350_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 this a read-only, idempotent, closed-world, non-destructive operation, so the safety profile needs no restating. The description does add one genuinely useful behavioral caveat — "The estimate assumes the same use and conditions as your measured period" — but says nothing about how the estimate is computed, what happens with out-of-range days, or what the result 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?

Three short sentences with no padding, and the caveat is placed sensibly at the end. However, the first sentence largely restates the name and title instead of front-loading the action, so the opening slot does not earn its place.

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 tool with five required numeric inputs, no output schema, and no annotations explaining units, the description is under-specified: an agent cannot tell what number comes back (monthly kWh? annual cost?) or what the measured-versus-projected window semantics are. It is enough to guess intent but not enough to call the tool confidently.

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 and mostly fails. Only offeredModel gets any meaning ("use the seller's model field or exact variant name"); measuredKwh, measuredDays, projectedDays, and tariffPerKwh are left entirely undefined — no units, no relationship between measured and projected windows, no tariff currency.

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 350 Luftbefeuchter" identifies the device but never states a clean verb+resource for what the tool does (record a purchase? project energy?). The energy-projection intent is only inferable from the title and from the closing sentence about estimates, and differentiation from the many sibling Levoit models rests entirely on the model name.

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-shaping advice for one parameter, not usage guidance. There is no statement of when to pick this model record versus a sibling model tool, and no prerequisites such as requiring an already-measured period before projecting.

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.