Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Levoit Classic 300S Ultraschall Luftbefeuchter

tds_purchase_m_levoit_levoit_classic_300s_luftbefeuchter
Read-onlyIdempotent

Recorded model Classic 300S Ultraschall 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_classic_300s_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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact: the estimate inherits the use pattern of the measured period. However, it does not clarify that nothing is persisted (despite the 'Recorded'/'purchase_m' framing) or how the projection is computed.

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 filler, which is good, but the lead sentence mostly restates the tool name/title, and the more valuable information (the projection assumption) is buried last. Reordering so the operation and its assumption come first would improve it without adding length.

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 required inputs, zero schema descriptions and no output schema, the definition leaves critical things unexplained: the unit and currency of tariffPerKwh, whether measuredDays must overlap the measured kWh, and what the response contains. For a computation tool whose whole value is the derived number, this is a substantial gap.

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 must carry the load. It only clarifies offeredModel (seller's model field or exact variant name) and gestures at the measured-vs-projected period relationship. measuredKwh, measuredDays, projectedDays and especially tariffPerKwh (currency? units?) remain undefined anywhere.

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 Classic 300S Ultraschall Luftbefeuchter" identifies the product variant but never states the verb or the output of the operation. The final sentence ("The estimate assumes the same use and conditions as your measured period") hints that a projection is produced, but an agent must infer that from the name rather than the description. It also does not distinguish itself from generic siblings such as tds_quote_climate_control.

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?

The only guidance is about which value to pass for one field ("Use the seller's model field or exact variant name"), which is parameter advice, not usage guidance. There is no statement of when this per-product projection tool should be chosen over a general projection or quote tool, and 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.