Skip to main content
Glama

The Doll Scout Home Tools

Estimate smart-home setup cost · Philips Hue Bridge

tds_purchase_b06
Read-onlyIdempotent

Recorded model Bridge 046677458478. 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_b06"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
unitPriceYes
deviceCountYes
offeredModelYes
hubAndAccessoriesYes
monthlyServicePriceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/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 scope, so the safety profile is covered and consistent with an estimation tool. The description adds modestly useful constraints (currency consistency, use the on-order amount) but says nothing about what the estimate contains or how the monthly/count terms combine.

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?

It is short with no filler, but it is structured as scattered imperative fragments rather than a front-loaded purpose sentence followed by constraints. The leading opaque model number consumes the most prominent position without helping the agent act.

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?

A six-parameter, all-required cost calculation with no output schema and no annotations explaining the computation demands more than this. The agent cannot tell how deviceCount, months, and monthlyServicePrice interact or whether the result is a total, a breakdown, or a stored record.

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 — yet it only clarifies offeredModel and unitPrice. deviceCount, hubAndAccessories, monthlyServicePrice and months (with its 1-120 bound) receive no explanation of units, meaning, or how they feed the estimate.

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; it opens with a bare identifier fragment ('Recorded model Bridge 046677458478') and then gives field-entry rules. The actual purpose (estimating smart-home setup cost) lives only in the title, so the description adds no verb+resource statement of its own.

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 input-level advice ('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'), but no guidance on when to select this tool versus the many sibling tds_purchase_* tools, and no exclusions. The agent must infer the selection context entirely.

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.