Skip to main content
Glama

The Doll Scout Home Tools

Check bathroom mounting clearance · iDesign Milo Shower Caddy

tds_purchase_m_idesign_milo_shower_caddy
Read-onlyIdempotent

Recorded model Milo Shower Caddy. Use the seller’s model field or exact variant name. Use measurements for the exact variant, including required clearances.

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>",
      "availableWidthCm": "<availableWidthCm>",
      "availableHeightCm": "<availableHeightCm>",
      "mountedWidthCm": "<mountedWidthCm>",
      "mountedHeightCm": "<mountedHeightCm>",
      "serviceMarginCm": "<serviceMarginCm>"
    },
    "name": "tds_purchase_m_idesign_milo_shower_caddy"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
mountedWidthCmYes
mountedHeightCmYes
serviceMarginCmYes
availableWidthCmYes
availableHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds almost nothing beyond that: it never states what is returned (a pass/fail fit result? the margin? a recommendation), nor how the service margin is applied to the decision.

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 and front-loaded, which is good, but the first sentence ("Recorded model Milo Shower Caddy") carries no actionable information and could be replaced with a single clause stating the tool's actual job.

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, no-output-schema tool, the description leaves the core logic opaque: what the numbers are compared against, what units the caller must assume, and what the result means. That leaves the agent guessing at the very thing the tool exists to decide.

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% for six required parameters, so the description must compensate and it largely does not. It hints at offeredModel ("seller's model field or exact variant name") and obliquely at serviceMarginCm ("required clearances"), but never distinguishes mountedWidthCm/mountedHeightCm (the product) from availableWidthCm/availableHeightCm (the wall space).

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 opens with "Recorded model Milo Shower Caddy," which restates the name/title rather than stating an action. It never says the tool checks whether the caddy fits the mounting space or returns a clearance verdict — the only hint at purpose is the word "clearances" in the second sentence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use the seller's model field or exact variant name" gives some context on how to identify the product, which implies this is a variant-scoped fit check. But it gives no when-to-use vs when-not guidance and names no alternative for cases where rough dimensions rather than a recorded model apply.

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.