Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · OXO Good Grips Expandable Dresser Drawer Divider Set

tds_purchase_a22
Read-onlyIdempotent

Recorded model 13227200. 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_a22"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already establish a safe, read-only, idempotent, closed-world operation. The description adds useful behavioral context that the model must be recorded/matched and the measurements must be for the exact variant including required clearances. It does not disclose the result format or what happens when the model does not match, so it remains only partially transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and free of filler, with specific model and measurement guidance front-loaded. It could be better structured by leading with the tool’s purpose, but it does not waste words.

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?

The tool has eight required parameters, no schema descriptions, and no output schema. The description provides some variant and clearance guidance but does not explain the fit-check logic, the roles of item versus inner dimensions, or what the tool returns. For this complexity, it is materially incomplete.

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%, so the description must carry parameter meaning. It helpfully clarifies that offeredModel should use the seller’s model field or exact variant name, and that measurements should correspond to the exact variant with clearances included. It does not explain the distinction between item dimensions, inner dimensions, and padding, leaving several required parameters to be inferred from property names.

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 title establishes a storage-fit check for a specific OXO product, and the description anchors it with model 13227200. However, the description itself never states what the tool does or what result it produces; it only gives model and measurement instructions, leaving the core action to be inferred from the title and parameter names.

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 tells the agent to use the seller’s model field or exact variant name and to use exact-variant measurements with clearances. That is input guidance, not selection guidance. It does not say when this product-specific fit tool should be used instead of sibling tools, nor does it mention any prerequisites or 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.