Skip to main content
Glama

The Doll Scout Home Tools

Estimate smart-home setup cost · Tapo C225 Pan/Tilt Home Security Camera

tds_purchase_b09
Read-onlyIdempotent

Recorded model C225. 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_b09"
  }
}

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 needs no restating. The description adds nothing beyond that: it does not say whether a stored estimate is created, whether it can be re-run or overwritten, or how 'months' and 'deviceCount' affect the result. No contradiction with the read-only annotations, but the burden created by the 0% parameter coverage is not shouldered.

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?

The description is short with no filler, which is good, but it is not front-loaded: it opens with a product identifier rather than a statement of the tool's function. The four clipped sentences read as scattered input hints rather than a structured explanation.

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?

There is no output schema, so the description should explain what the six inputs produce (a cost estimate, its components, units). It does not, and with all six parameters required and undocumented in the schema, an agent cannot confidently construct a correct call from the description alone.

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?

With 0% schema description coverage on six required parameters, the description must compensate. It clarifies offeredModel (seller's model field or exact variant name) and gives currency guidance relevant to unitPrice, hubAndAccessories and monthlyServicePrice, but says nothing about deviceCount or months, and nothing about what hubAndAccessories covers. Half of the parameters remain entirely undocumented.

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: no verb such as 'estimate' or 'calculate', and no mention of setup cost or totals. Only the title ('Estimate smart-home setup cost') carries that meaning, and the description itself merely identifies the product variant ('Recorded model C225'). An agent reading only the description cannot tell this apart from a plain purchase-record tool.

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?

All guidance concerns data entry ('Use the seller's model field or exact variant name', 'Enter prices in the same currency'), not when to select this tool versus the many sibling purchase tools. There is no statement of context, prerequisites, or exclusions for invocation.

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.