Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Yamazaki Wall-Mounted Shelf Round

tds_purchase_m_yamazaki_wall_mounted_shelf_round
Read-onlyIdempotent

Recorded model Wall-Mounted Shelf Round. 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>",
      "itemWidthCm": "<itemWidthCm>",
      "itemDepthCm": "<itemDepthCm>",
      "itemHeightCm": "<itemHeightCm>",
      "innerWidthCm": "<innerWidthCm>",
      "innerDepthCm": "<innerDepthCm>",
      "innerHeightCm": "<innerHeightCm>",
      "paddingCm": "<paddingCm>"
    },
    "name": "tds_purchase_m_yamazaki_wall_mounted_shelf_round"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds a meaningful correctness constraint — results are only valid for the exact variant and must include required clearances — but says nothing about what the fit result looks like or what happens when clearances are insufficient.

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 padding, but the first sentence is a wasted tautology of the product name. The actionable guidance is present yet not front-loaded or grouped by parameter group.

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 per-variant fit-check tool with 8 required measurements, no output schema, and 0% schema coverage needs the description to define item vs inner dimensions and the padding/clearance parameter. None of that is present, so an agent must guess at the most consequential inputs.

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 8 required numeric parameters, so the description carries the burden and mostly fails. It hints that offeredModel takes the seller's model field or variant name and that clearances matter, but never explains the item-versus-inner dimension pairs or what paddingCm represents, leaving the core distinction undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence, "Recorded model Wall-Mounted Shelf Round," merely restates the product name and never says what the tool does with it. The reference to measurements and required clearances implies a fit/storage check, so an agent can infer purpose, but only via the title and schema rather than an explicit verb.

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 description gives input-selection advice ("Use the seller's model field or exact variant name", "Use measurements for the exact variant") but no when-to-use or when-not guidance. Nothing distinguishes this from sibling product-fit tools or points to an alternative when the variant is unknown.

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.