Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · iDesign RPET Linus Binz 7

tds_purchase_m_idesign_rpet_linus_binz_7
Read-onlyIdempotent

Recorded model RPET Linus Binz 7. 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_idesign_rpet_linus_binz_7"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that measurements must match the exact variant and that clearances are required (mapping to paddingCm), which is useful context, but it never explains what the result means (fit/no-fit criteria) or how item and inner dimensions interact.

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 a redundant restatement of the title, and the genuinely useful instructions are pushed to the back rather than front-loaded.

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 an 8-parameter, fully-required tool with no output schema and zero schema descriptions, the description is too thin: it omits the item-vs-inner dimension distinction, the meaning of padding, and what the computed result represents. An agent could populate the fields but would likely misuse the measurement parameters.

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 numeric/string parameters, so the description must compensate. It only clarifies offeredModel and gestures at measurements/clearances; it never distinguishes itemWidthCm/itemDepthCm/itemHeightCm from innerWidthCm/innerDepthCm/innerHeightCm, which is the single most ambiguous point in the schema.

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?

The description opens with a label ("Recorded model RPET Linus Binz 7") that merely restates the title rather than stating an action such as checking whether an item fits a storage space. No verb names what the tool computes or returns, so an agent must infer purpose from the title and parameter names alone.

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?

It gives input-population guidance (use the seller's model field or exact variant name; use measurements for the exact variant) which implies the usage context of variant-specific fit checking. It does not, however, say when to prefer this over related siblings such as tds_accessory_fit_through_lip or tds_quote_storage_space, nor 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.