Skip to main content
Glama

The Doll Scout Home Tools

Estimate smart-home setup cost · Philips Hue indoor Motion sensor

tds_purchase_b07
Read-onlyIdempotent

Recorded model Motion sensor 046677570972. 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_b07"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
unitPriceYes
deviceCountYes
offeredModelYes
hubAndAccessoriesYes
monthlyServicePriceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/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 a closed world, so the safety profile is covered externally. The description adds one genuine behavioral constraint — prices must be in a single currency, implying no conversion is performed — but says nothing about how the estimate is computed (whether monthlyServicePrice is multiplied by months, whether hubAndAccessories is added) or what is returned, despite there being no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short but not front-loaded: the opening sentence is an opaque SKU fragment that conveys no action, and the remaining sentences are unordered data-entry caveats. No sentence establishes the operation before the constraints, so brevity here reflects under-specification rather than economy.

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 calculation tool with no output schema and zero schema coverage, the description should at minimum state what is being computed and how the inputs combine. It instead provides two narrow input conventions, leaving the agent unable to predict the result of a call or confirm the units of four parameters.

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 carries the full burden and largely fails it. Only offeredModel and unitPrice get any semantic help ("seller's model field or exact variant name", "amount that will appear on the order"); deviceCount, hubAndAccessories, monthlyServicePrice and months are never mentioned, leaving their units and meaning to guesswork.

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 resource. "Recorded model Motion sensor 046677570972" is a fragment identifying a product SKU, and the only clue about function ("Estimate smart-home setup cost") lives in the title, not the description. An agent reading only the description could not tell this computes a cost estimate rather than looking up a product.

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, when-not-to-use, or alternative-tool guidance despite ~30 similarly named tds_purchase_* siblings. The sentences present are data-entry rules for parameters (use seller's model field, keep currency consistent), not selection guidance.

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.