Skip to main content
Glama

The Doll Scout Home Tools

Estimate cleaning upkeep cost · SwitchBot S Series Dust Bag

tds_purchase_m_switchbot_s_series_dust_bag
Read-onlyIdempotent

Recorded model S Series Dust Bag. Use the seller’s model field or exact variant name. Enter prices in the same currency. Use the amount that will appear on the order.

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>",
      "starterPrice": "<starterPrice>",
      "replacementPackPrice": "<replacementPackPrice>",
      "usesPerPack": "<usesPerPack>",
      "remainingUses": "<remainingUses>"
    },
    "name": "tds_purchase_m_switchbot_s_series_dust_bag"
  }
}

Input Schema

NameRequiredDescriptionDefault
usesPerPackYes
offeredModelYes
starterPriceYes
remainingUsesYes
replacementPackPriceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/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 safety is covered, but the description adds essentially no behavior beyond them: it does not say the tool only computes rather than records a purchase, that no order is placed, or that the result is an estimate based on the supplied prices and use counts.

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?

Four terse sentences with little wasted wording, but the structure is not front-loaded: the first sentence is a product-name restatement instead of the purpose, and the remaining sentences are rules without a stated operation to attach them to.

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-required-parameter computation tool with no output schema and no parameter descriptions, so the description must explain the calculation and what comes back. It instead leaves the cost formula, the meaning of two of the five inputs, and the return shape entirely unspecified.

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?

With 0% schema description coverage across 5 required parameters, the description must carry parameter meaning and mostly does not. It clarifies offeredModel (seller's model field or exact variant name) and imposes a same-currency/order-amount rule on the two price fields, but usesPerPack and remainingUses are never explained, and which price is the starter versus replacement pack is left ambiguous.

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?

"Recorded model S Series Dust Bag" restates the product name from the title rather than stating what the tool does. Only the title ("Estimate cleaning upkeep cost") conveys the operation, and the description never says it computes an upkeep/consumable cost estimate or what it produces; nothing distinguishes it from the dozens of sibling per-product cost tools.

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 sentences give data-entry rules (use the seller's model field or exact variant name, keep currency consistent, use the on-order amount) but no guidance on when this tool applies versus other product tools or what inputs make a meaningful estimate. Useful only as hygiene hints, not as usage selection guidance.

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.