Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Levoit Vital 200S Pro Luftreiniger

tds_purchase_m_levoit_levoit_vital_200s_luftreiniger
Read-onlyIdempotent

Recorded model Vital 200S Pro Luftreiniger. 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_vital_200s_luftreiniger"
  }
}

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one genuine behavioral caveat - the estimate assumes identical use conditions to the measured period - which is useful context, but it omits how the projection is computed and what the result represents.

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, but the opening sentence largely restates the tool name/title and delivers little information relative to the space it occupies. The one substantive caveat is buried last rather than front-loaded.

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-parameter, no-output-schema projection tool needs at least units (kWh, days, currency per kWh) and a hint about what is returned. The description supplies neither, so an agent cannot reliably populate four of the five required fields from this text alone.

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. The description only addresses offeredModel (exact variant naming); measuredKwh, measuredDays, projectedDays and tariffPerKwh get no units, ranges or meaning, leaving most parameters undocumented 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 Vital 200S Pro Luftreiniger" identifies the product variant but never states the operation - that measured kWh is projected forward over a projected period at a given tariff. An agent must infer the verb from the title ("Project measured climate-device energy") rather than the description.

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 value-selection guidance for one parameter, not when-to-use guidance. There is no statement of when this tool applies versus the many sibling per-product energy tools, and no prerequisites or exclusions.

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.