Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · Levoit Neoclassic 450S Luftbefeuchter

tds_purchase_m_levoit_levoit_neoclassic_450s_luftbefeuchter
Read-onlyIdempotent

Recorded model Neoclassic 450S 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_450s_luftbefeuchter"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context by disclosing the modeling assumption that use and conditions match the measured period. It does not, however, describe what the tool returns (a projected kWh figure? a cost?) despite there being no output schema.

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?

Two short sentences with no padding, which is appropriately sized. But the first sentence is pure restatement of the title and the guidance for offeredModel is buried after it rather than front-loaded with the actual operation.

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 parameters, 0% schema coverage and no output schema, the description should explain units, the projection method, and what is returned. It supplies only a validity caveat, leaving an agent unable to predict the result shape or confirm units for kWh/tariff inputs.

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%, so the description must carry parameter meaning and it largely fails. It clarifies only offeredModel (use the seller's model field or exact variant name) and gestures at the relationship between measured and projected periods; it says nothing about units or interpretation for measuredKwh, tariffPerKwh, or whether projection extrapolates linearly across projectedDays.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with "Recorded model Neoclassic 450S Luftbefeuchter," which only restates the title's product name and never states the action the tool performs. No verb such as 'compute', 'project', or 'estimate' appears, so an agent must infer from the title and required fields (measuredKwh, measuredDays, projectedDays, tariffPerKwh) that this projects energy/cost.

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" gives input guidance for offeredModel, and the final sentence scopes when the estimate is valid. However, there is no statement of when to call this tool versus the many sibling per-product variants, and no preconditions or exclusions are given.

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.