Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Yamazaki Tissue Case Square

tds_purchase_m_yamazaki_tissue_case_square
Read-onlyIdempotent

Recorded model Tissue Case Square. 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_tissue_case_square"
  }
}

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?

The annotations already show that this is a read-only, idempotent, non-destructive operation in a closed world, so the safety profile needs no extra explanation. What the description omits is the result: there is no output schema, so the description ought to say whether this tool returns a boolean fit verdict, a list of clearance violations, or the largest acceptable variant. With the annotations carrying the safety profile, a 3 is warranted.

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 are efficient and lose nothing structurally, but the first sentence ("Recorded model Tissue Case Square") conveys no load-bearing information and pushes the only useful content back to later sentences. The definition is short, but it is not well front-loaded because the purpose sentence is missing.

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?

An 8-parameter, all-required computation with no output schema and no schema descriptions depends heavily on the description, yet the description never says what the tool computes or returns, never distinguishes item from inner dimensions, and never explains paddingCm. For this complexity, the definition is materially incomplete, even though the annotations adequately cover side effects.

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 8 required parameters, but the description documents only offeredModel (seller's model field or exact variant name) and only vaguely mentions "required clearances" in place of paddingCm. It never explains the relationship among the itemWidthCm, itemDepthCm and itemHeightCm trio, the innerWidthCm, innerDepthCm and innerHeightCm trio, and paddingCm, so an agent must infer whether item* describes the product and inner* describes the container. The description therefore compensates very little for the empty schema.

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 Tissue Case Square," simply restates the tool name and adds no new information. Only the later phrase "including required clearances" hints that this tool checks whether the item fits, and the description never states that purpose outright. Because the sibling names follow a tds_purchase_m_<product> pattern, an agent can infer that this tool belongs to a family rather than a fit-check tool, so the purpose is only partly clear.

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?

"Use the seller's model field or exact variant name" is data-entry guidance for one parameter, not guidance about when to use this tool versus fit-check siblings such as tds_accessory_fit_through_lip or tds_quote_storage_space. The description gives no condition that selects this tool, no prerequisites, and no exclusions.

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.