Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Yamazaki Magnetic Shelf

tds_purchase_m_yamazaki_10094_tower_magnetic_shelf
Read-onlyIdempotent

Recorded model Magnetic Shelf. 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_10094_tower_magnetic_shelf"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description only needs to add context. It does add two useful facts: results are variant-specific and required clearances are factored in. It never says what the check produces (a pass/fail, a margin, a list) and has no output schema to fall back on.

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, but the lead sentence is the least informative part and the actionable constraint (exact variant, clearances) is buried at the end. Front-loading the purpose would make the same word count far more useful.

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?

Eight required numeric/string parameters with zero schema documentation, no output schema, and a description that explains fewer than half of them. For a fit-computation tool where mixing outer item dimensions with inner cavity dimensions is the main failure mode, this is materially under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 8 required parameters, so the description must carry the load. It partially does: offeredModel is tied to "the seller's model field or exact variant name," item dimensions are implied by "measurements," and paddingCm maps to "required clearances." The three inner* parameters are never explained, nor is the relationship between item and inner dimensions.

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?

"Recorded model Magnetic Shelf" mostly restates the product named in the title and never states an action verb or what the tool actually computes. The remaining sentences describe how to fill in inputs, not what the tool does, so an agent cannot tell from the text that this checks whether an item fits a space.

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-sourcing advice ("use the seller's model field or exact variant name") rather than when to use this tool versus alternatives. No condition, prerequisite, or sibling is named, despite siblings like tds_accessory_fit_through_lip and tds_quote_storage_space existing in the same family.

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.