Skip to main content
Glama

The Doll Scout Home Tools

Estimate smart-home setup cost · Tapo H100 Smart IoT Hub

tds_purchase_b14
Read-onlyIdempotent

Recorded model H100. 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_b14"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
unitPriceYes
deviceCountYes
offeredModelYes
hubAndAccessoriesYes
monthlyServicePriceYes

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. The description adds only that amounts should match the eventual order and that currencies must be consistent — it does not say what is computed, whether this is a simulation or a real purchase (a real ambiguity given the 'tds_purchase' name), or what the response contains.

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 filler, but they are unstructured fragments rather than a front-loaded statement of purpose followed by constraints. The first sentence ('Recorded model H100') is the least informative yet placed first, which hurts scannability.

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 six required parameters, no schema descriptions, and no output schema, the description should explain the cost model and the return value; it does neither. It also leaves unexplained whether hubAndAccessories is a flat cost or per-device, and how monthlyServicePrice × months participates in the estimate. Only the model-string and currency conventions are adequately covered.

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 the load, but it only addresses two of six parameters: offeredModel (use the seller's field or exact variant name) and the price fields' currency/value convention. DeviceCount, hubAndAccessories, monthlyServicePrice, and months — including their bounds and how hub cost relates to device count — get no explanation anywhere.

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; the only signal of purpose is the title 'Estimate smart-home setup cost.' The body opens with the opaque fragment 'Recorded model H100' and then gives input instructions, so an agent must infer the verb from the title alone. It does pin the resource to a single fixed product ('H100'), which is the one distinct piece of information.

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 'Enter prices in the same currency' are input-entry rules, not guidance about when to call this tool versus the many sibling purchase tools. There is no statement of prerequisites, when-not-to-use, or how this differs from other Tapo/product variants.

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.