Skip to main content
Glama

The Doll Scout Home Tools

Check straight-in case fit · Accessory through a rigid lip

tds_accessory_fit_through_lip
Read-onlyIdempotent

Compare the entry and case interior in both allowed horizontal orientations. Accessory through a rigid lip. Reserve for the retaining lip (mm).

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": {
      "doorWidthMm": "<doorWidthMm>",
      "doorHeightMm": "<doorHeightMm>",
      "insideWidthMm": "<insideWidthMm>",
      "insideDepthMm": "<insideDepthMm>",
      "insideHeightMm": "<insideHeightMm>",
      "itemWidthMm": "<itemWidthMm>",
      "itemDepthMm": "<itemDepthMm>",
      "itemHeightMm": "<itemHeightMm>",
      "allowsTurn": "<allowsTurn>",
      "retainingLipReserveMm": "<retainingLipReserveMm>"
    },
    "name": "tds_accessory_fit_through_lip"
  }
}

Input Schema

NameRequiredDescriptionDefault
allowsTurnYes
doorWidthMmYes
itemDepthMmYes
itemWidthMmYes
doorHeightMmYes
itemHeightMmYes
insideDepthMmYes
insideWidthMmYes
insideHeightMmYes
retainingLipReserveMmYes

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 declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that both allowed horizontal orientations are compared and that a retaining-lip reserve is involved, but it does not say whether the tool returns a boolean fit result, measurements, or other output. It adds some context without contradicting annotations.

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

Conciseness2/5

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

The description is only three sentences, but the second ('Accessory through a rigid lip') repeats the name/title and the third ('Reserve for the retaining lip (mm)') is a cryptic fragment. The opening sentence is front-loaded, yet the rest does not build a clear sequence of use. It is short but not efficient because it omits needed meaning while including redundancy.

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 10-required-parameter geometric fit check with no output schema, the description is far too thin. It does not define the dimensions, orientation behavior, or what the result represents, leaving the agent unable to invoke it confidently without guessing parameter meanings. Annotations cover only safety, not the missing operational detail.

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?

With 10 required parameters and 0% schema description coverage, the description must explain each parameter. It only vaguely maps 'entry and case interior' to door/inside dimensions, 'Accessory' to item dimensions, and 'retaining lip (mm)' to retainingLipReserveMm; allowsTurn and the individual dimension roles remain unexplained. The '(mm)' unit is useful but insufficient across ten required inputs.

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 opens with 'Compare the entry and case interior in both allowed horizontal orientations,' which states an action and the objects being compared. However, 'Accessory through a rigid lip' is a noun fragment rather than a clear statement of what is checked or what result is produced, and much of the specificity comes from the title. It is loosely distinguishable from generic case-opening siblings, but not sharply defined.

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?

There is no explicit when-to-use or when-not-to-use guidance. 'Reserve for the retaining lip (mm)' reads as a parameter note rather than a usage rule, and no alternative fit-checking tool is named. The agent must infer that this is for straight-in accessory fit through a rigid lip.

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.