Skip to main content
Glama

The Doll Scout Home Tools

Estimate smart-home setup cost · Philips Hue Smart plug

tds_purchase_b08
Read-onlyIdempotent

Recorded model Smart plug 046677552343. 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_b08"
  }
}

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 safety is covered and the description does not need to restate it. Beyond that, the description discloses nothing: it never says whether an estimate is returned, how hubAndAccessories or monthlyServicePrice are combined, or what the result looks like — and there is no output schema to compensate. 'Recorded model' is also ambiguous about whether anything is persisted.

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, and the model identifier is front-loaded. However, the space is spent on data-entry etiquette rather than on stating the operation or the parameters that actually need explanation, so brevity comes at the cost of usefulness.

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-required-parameter estimator with no output schema and 0% schema description coverage, the description should explain the computation model and the meaning of at least the cost and duration inputs. It covers two parameters and never states that the tool produces an estimate, leaving the agent to guess what the call returns.

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 semantics and it only partially does. It clarifies offeredModel ('seller's model field or exact variant name') and unitPrice (currency and amount conventions), but says nothing about deviceCount, hubAndAccessories (one-time total or per-device?), monthlyServicePrice, or months, which are the genuinely ambiguous inputs.

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, no mention of estimating or computing a cost, only the recorded model number and data-entry conventions. The purpose ('Estimate smart-home setup cost') exists only in the title, so an agent must infer the operation from the title plus the parameter names. The model identifier 046677552343 is the only concrete scope cue.

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 when-to-use or when-not-to-use guidance, and no differentiation from the many sibling tds_purchase_* tools despite the name pattern suggesting they are near-duplicates. The 'same currency' and 'amount that will appear on the order' remarks govern input format rather than tool selection, so an agent gets no help choosing this tool over a sibling.

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.