Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Levoit Classic36AC Turmventilator Schwarz

tds_purchase_m_levoit_levoit_classic36ac_turmventil_89a8f467
Read-onlyIdempotent

Recorded model Classic36AC Turmventilator Schwarz. 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_classic36ac_turmventil_89a8f467"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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 agent knows this is a safe, repeatable computation with no side effects; the description need not restate that. What it does add is the key behavioral caveat that the projection assumes identical usage conditions to the measured period, which is genuinely valuable for interpreting the result. It stops short of saying what the output contains (projected kWh vs. cost) or how tariffPerKwh affects the result, leaving a gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler; the model identification comes first, followed by the input-selection rule and the assumption caveat. Slightly wasteful in that the first sentence largely duplicates the title, but the remaining two sentences each carry real 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?

This is a five-parameter required-input computation with no output schema and no parameter descriptions in the schema, so the description is the only place an agent could learn what is returned and what the inputs mean. It covers the model-name rule and the assumption caveat but says nothing about the return value (projected consumption and/or cost) or the units and interaction of the numeric inputs, leaving the definition under-specified for its complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden, and it only addresses one of five required parameters — offeredModel — telling the agent to use the seller's model field or exact variant name. The other four (measuredKwh, measuredDays, projectedDays, tariffPerKwh) are self-descriptive by name and bounded by min/max in the schema, but neither schema nor description explains units or how measured vs. projected days interact, so the description only partially compensates for the coverage gap.

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 title states 'Project measured climate-device energy' and the description pins the exact variant ('Recorded model Classic36AC Turmventilator Schwarz'), so the resource is unambiguous and distinguishable from the many sibling product variants. However, the description itself never states the operation with a verb — the projection is only implied by 'The estimate assumes the same use and conditions as your measured period' — so an agent reading the description alone must infer that this scales measured consumption to a projected period.

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 directive is 'Use the seller's model field or exact variant name,' which is guidance about how to fill one parameter, not about when to choose this tool over an alternative. There is no statement of prerequisites, no mention of when the projection is inappropriate, and no routing to sibling tools (e.g. the other Levoit tower-fan variants or tds_quote_climate_control).

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.