Skip to main content
Glama

The Doll Scout Home Tools

Estimate smart-home setup cost · Tapo T310 Smart Temperature and Humidity Sensor

tds_purchase_b12
Read-onlyIdempotent

Recorded model T310. 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_b12"
  }
}

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 and destructiveHint=false, so the safety profile is covered. The description adds nothing about the central behavioral question raised by the name "purchase": whether an order is placed or only a cost is calculated, how the total is derived from deviceCount, hubAndAccessories, monthlyServicePrice and months, or what is returned (no output schema exists). Currency/order-amount rules are useful but do not disclose behavior.

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, which is good. However the opening line ("Recorded model T310") is cryptic and front-loads an identifier rather than the action, so the structure buries what little value the text carries.

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, all-required estimation tool with no output schema and no schema descriptions, the definition is materially incomplete: four of six inputs are unexplained and the calculation the tool performs is never described. An agent could not confidently predict results or verify a correct call from this description.

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 six required parameters, so the description must carry the burden. It only partially does: offeredModel (seller's model field or exact variant name) and unitPrice (same currency, amount shown on the order) get guidance, while deviceCount, hubAndAccessories, monthlyServicePrice and months receive no explanation at all, leaving the cost formula and the meaning of the service-fee inputs undefined.

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 body never states what the tool does; it opens with the fragment "Recorded model T310" and then gives only input-entry rules. The action ("Estimate smart-home setup cost") exists only in the title, so an agent reading the description alone cannot tell this is a cost estimator rather than a purchase/order action. The product specification (T310) does distinguish it from the many sibling per-product tools, but that differentiation comes from the name, not the prose.

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?

Guidance is limited to data entry ("use the seller's model field or exact variant name", "enter prices in the same currency"), which tells the agent how to fill fields but not when to pick this tool over the dozens of tds_purchase_m_* siblings or the tds_purchase_a0x tools. No prerequisites, no exclusions, and no statement about what happens if the wrong variant is supplied.

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.