Skip to main content
Glama

The Doll Scout Home Tools

Estimate cleaning upkeep cost · Tapo RV30 MAX

tds_purchase_m_tapo_tapo_rv30_max_turbo
Read-onlyIdempotent

Recorded model RV30 MAX. 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_tapo_tapo_rv30_max_turbo"
  }
}

Input Schema

NameRequiredDescriptionDefault
usesPerPackYes
offeredModelYes
starterPriceYes
remainingUsesYes
replacementPackPriceYes

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds two genuinely useful behavioral constraints not in the annotations: prices must share one currency and the amount must match what appears on the order. It says nothing about the computation performed or the shape of the result.

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?

Four short sentences, no filler, and the model constraint is front-loaded. The opening sentence is slightly awkward — it reads as a fragment rather than a purpose statement — but nothing is wasted.

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 definition should explain what the estimate returns and what the two usage-count parameters mean. Instead it covers only naming and currency conventions, leaving an agent unable to predict the response or understand half the inputs.

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 coverage is 0%, so the description carries the full burden, and it only partially delivers. It clarifies offeredModel (seller's model field or exact variant name) and constrains the two price fields (same currency, order amount), but usesPerPack and remainingUses — the inputs that drive the estimate — are left entirely unexplained.

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 never states what the tool does; its first sentence ("Recorded model RV30 MAX") merely names the product, and the rest is input-filling advice. The actual action — estimating cleaning upkeep cost — appears only in the title, not in the description text. It does at least pin the tool to one specific model, distinguishing it from the RV30 MAX Plus Gen 2 sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Guidance is present but only about how to fill inputs (use the seller's model field or exact variant name, keep prices in one currency), not about when to call this tool versus a sibling. The model-locking statement implicitly routes the agent to the matching per-product variant, but no explicit alternative or exclusion is 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.