Skip to main content
Glama

The Doll Scout Home Tools

Check bathroom mounting clearance · iDesign Pebblz Bath Mat Green

tds_purchase_m_idesign_pebblz_bath_mat_green
Read-onlyIdempotent

Recorded model Pebblz Bath Mat Green. 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_pebblz_bath_mat_green"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
mountedWidthCmYes
mountedHeightCmYes
serviceMarginCmYes
availableWidthCmYes
availableHeightCmYes

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, so the safety profile is covered structurally. The description adds nothing beyond that: no indication of what a call returns, what happens when clearances fail, whether a passing/failing verdict is produced, or any constraint specific to this operation. For a check/verification tool, the pass/fail semantics are the key behavioral fact and they are absent.

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 product identity front-loaded, so it is efficiently sized. However, the brevity comes at the cost of under-specification rather than being information-dense, so the structure is clean but the content is thin.

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?

With six required parameters at 0% schema coverage, no output schema, and no explanation of the clearance-check result, the description is not sufficient for an agent to invoke this correctly. An agent cannot determine the relationship between the four width/height fields or the role of the service margin without guessing.

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 numeric parameters, so the description carries the full burden and fails to meet it. It loosely gestures at offeredModel ("seller's model field or exact variant name") and at the measurement parameters, but never distinguishes availableWidthCm/availableHeightCm from mountedWidthCm/mountedHeightCm, nor explains what serviceMarginCm represents or its units.

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 an action verb; it opens with "Recorded model Pebblz Bath Mat Green," which merely restates the product in the tool name/title. Only the title hints at the real purpose (checking mounting clearance), and an agent reading the description alone cannot tell whether this records, verifies, or purchases anything. It is effectively a tautology of the name.

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?

The two guidance sentences ("Use the seller's model field or exact variant name," "Use measurements for the exact variant") describe input formatting, not when to select this tool over the many sibling product tools. There is no statement of preconditions, when-not-to-use, or how it relates to other iDesign product tools in the catalog.

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.