Skip to main content
Glama

The Doll Scout Home Tools

Estimate cleaning upkeep cost · Tapo RV50 PRO

tds_purchase_m_tapo_tapo_rv50_pro_omni
Read-onlyIdempotent

Recorded model RV50 PRO. 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_rv50_pro_omni"
  }
}

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description's only added behavior is the same-currency rule. Critically, with no output schema, the description must explain what is produced, and it never says whether the result is a per-cycle cost, a monthly cost, a pack count, or a formatted string — a major disclosure gap for a calculation tool.

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 short sentences with no padding, and the actionable constraints are easy to scan. However, the lead sentence 'Recorded model RV50 PRO' repeats what the tool name and title already establish and occupies the highest-value position where the tool's purpose should sit.

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?

For a five-parameter, fully-required estimation tool with zero schema documentation and no output schema, the description omits two things an agent cannot get elsewhere: how the inputs combine into an estimate, and what the response contains. It reads as partial form-validation guidance rather than a usable tool definition.

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 5 required numeric/string parameters, so the description carries the full burden. It clarifies offeredModel (seller's model field or exact variant name) and constrains the two price fields to one currency and to the on-order amount, but 'usesPerPack' and 'remainingUses' — the two values that drive any upkeep math — are never explained, and the relationship between them and the price fields is left to inference.

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. It opens with 'Recorded model RV50 PRO' and proceeds to data-entry rules; nothing says it estimates or computes a cleaning upkeep cost — that framing exists only in the title. An agent reading only the description cannot tell whether this records a purchase, computes a total, or validates inputs.

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' and 'Use the amount that will appear on the order' give input-selection rules, which is useful. But there is no when-to-use guidance, no condition distinguishing this from the ~30 sibling tds_purchase_m_* tools, and no statement of prerequisites or when the estimate should be recomputed.

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.