Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Levoit Eleva® 300X Luftreiniger

tds_purchase_m_levoit_levoit_eleva_300x_luftreiniger
Read-onlyIdempotent

Recorded model Eleva® 300X 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_eleva_300x_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, closed-world behavior, so the safety profile is covered. The description adds one genuinely useful behavioral caveat — that the projection carries the assumptions of the measured period — which is context the annotations do not convey. It does not disclose how the projection is computed, what unit the result takes, or any limits, leaving real gaps.

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 lead sentence is pure repetition of the tool name and product title, so the useful content (model-name convention and the assumption caveat) is buried. Nothing is verbose, but the front-loading is spent on redundant information.

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 projection tool with no output schema and no annotation-level detail about results needs the description to explain the measured-versus-projected relationship and the tariff input. It explains none of that, so an agent would have to guess how the parameters combine and what comes back.

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 burden and largely does not. It addresses only offeredModel (accept the seller's model field or exact variant name) and says nothing about measuredKwh, measuredDays, projectedDays, or tariffPerKwh — the four parameters that define the projection itself.

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 first sentence only restates the model identity already encoded in the tool name; the operative verb is never stated. "The estimate assumes the same use and conditions as your measured period" implies the tool produces some kind of energy projection, but an agent cannot tell whether it returns kWh, cost, or savings from the description alone. Siblings differ only by product name, so differentiation via the model string is at least present.

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. There is no statement of when this projection tool is appropriate versus the sibling product variants or versus tds_quote_climate_control, and no preconditions are given beyond the measurement-period assumption.

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.