Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Lifewit Slim Laundry Hamper

tds_purchase_m_lifewit_lifewit_slim_laundry_hamper
Read-onlyIdempotent

Recorded model Slim Laundry Hamper. 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_lifewit_lifewit_slim_laundry_hamper"
  }
}

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
Behavior2/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false and closed-world, so the safety profile is fully covered by structured data and the description does not contradict it ("Recorded model" is consistent with a read of stored data). Beyond that the description adds almost nothing: no indication of what is computed or returned (there is no output schema), no failure modes for a mismatched variant, and no explanation of how clearance/padding affects the result.

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, which is good. However "Recorded model Slim Laundry Hamper" is grammatically awkward and reads as a data label rather than an instruction, making the opening sentence harder to parse than its length warrants.

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?

For a tool with 8 required numeric/string parameters, no parameter descriptions and no output schema, the description is too thin: an agent still cannot tell what item vs. inner measurements mean, what padding does, or what the response contains. It answers almost none of the questions the structured fields leave open.

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, so the description carries the full explanatory burden and largely fails it. It only loosely maps to two inputs (offeredModel via "seller's model field or exact variant name", paddingCm via "required clearances"); the crucial distinction between item* and inner* dimensions, and how padding is applied, is never explained.

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 description names the exact product ("Slim Laundry Hamper") and signals that a model entry and its measurements are involved, which helps distinguish it from the other per-product siblings. But the operative verb is missing: "Recorded model..." does not say whether the tool records dimensions, looks up a stored model, or evaluates fit (only the title hints at "Check storage fit"). An agent can guess the resource but not confidently the action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/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" and "Use measurements for the exact variant, including required clearances" give real input-selection guidance. What is absent is any when-to-use framing against the numerous sibling hamper/storage tools, or any statement of preconditions (e.g., that a matching recorded model must exist).

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.