Skip to main content
Glama

The Doll Scout Home Tools

Estimate smart-home setup cost · Tapo D225 Smart Wi-Fi Video Doorbell

tds_purchase_b10
Read-onlyIdempotent

Recorded model D225. 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>",
      "unitPrice": "<unitPrice>",
      "deviceCount": "<deviceCount>",
      "hubAndAccessories": "<hubAndAccessories>",
      "monthlyServicePrice": "<monthlyServicePrice>",
      "months": "<months>"
    },
    "name": "tds_purchase_b10"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
unitPriceYes
deviceCountYes
offeredModelYes
hubAndAccessoriesYes
monthlyServicePriceYes

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 readOnly=true, idempotent=true, destructive=false, openWorld=false, so the safety profile is covered. The description adds little beyond that: it implies consistent-currency input and order-matching amounts, but never says the tool returns an estimate rather than creating an order, nor what the computation is. Nothing contradicts the annotations, so no contradiction flag.

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?

Three short sentences with no filler, but the ordering is poor: the first sentence records a model rather than stating the tool's purpose, so the agent hits detail before context. It is terse to the point of under-specification rather than efficient.

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 six-parameter, fully-required calculation tool with no output schema and zero schema coverage, the description should explain the cost formula and each input's role. Instead it leaves four parameters undefined and never states that the output is an estimate, so an agent cannot reliably produce correct 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 carries the full burden across six required parameters. It meaningfully explains only offeredModel (use the seller's model field or exact variant name) and the price fields (same currency, amount that will appear on the order). deviceCount, hubAndAccessories, monthlyServicePrice and months are completely unexplained, including how months interacts with the monthly service price.

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 D225" and then gives data-entry rules. The actual action (estimating a smart-home setup cost) appears only in the title, so an agent cannot learn the verb+resource from the description itself. It also gives no basis for distinguishing this from the many sibling per-product purchase/estimate 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?

There is no statement of when to use this tool versus the dozens of sibling tds_purchase_m_* product tools. The only guidance is about how to fill fields, not about tool selection or preconditions. An agent must infer applicability from the title alone.

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.