Skip to main content
Glama

The Doll Scout Home Tools

Check straight-in case fit · Small display cabinet aperture

tds_cabinet_door
Read-onlyIdempotent

Compare the entry and case interior in both allowed horizontal orientations. Small display cabinet aperture. Hinge clearance at the opening (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>",
      "doorHingeReserveMm": "<doorHingeReserveMm>"
    },
    "name": "tds_cabinet_door"
  }
}

Input Schema

NameRequiredDescriptionDefault
allowsTurnYes
doorWidthMmYes
itemDepthMmYes
itemWidthMmYes
doorHeightMmYes
itemHeightMmYes
insideDepthMmYes
insideWidthMmYes
insideHeightMmYes
doorHingeReserveMmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so safety and semantics are largely covered. Beyond that, the description only adds that both horizontal orientations are evaluated and that hinge clearance at the opening matters — it does not say what a pass/fail decision is based on, whether a single result or per-orientation results are returned, or how the hinge reserve is applied. With annotations carrying the safety burden, this is still thin.

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?

It is short and front-loaded with the operative sentence, which is good. But the remaining two sentences are noun fragments rather than informative statements, so brevity comes at the cost of structure and readability — a fragmented definition, not a tight one.

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?

This is a 10-required-parameter geometric computation with no output schema and no annotations describing results, so the description must explain inputs and the shape of the outcome. It does neither: an agent cannot tell what the return value looks like (boolean, per-orientation verdicts, clearance margins) or how to interpret a failure.

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 10 required numeric parameters, so the description must compensate and largely does not. Only two parameters get any interpretive help: 'both allowed horizontal orientations' hints at allowsTurn, and 'Hinge clearance at the opening (mm)' hints at doorHingeReserveMm. The eight dimension parameters (door, inside, and item width/depth/height) are left entirely to names and min/max bounds, with no explanation of units conventions or how door vs. inside vs. item dimensions interact.

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 first sentence names the operation reasonably well: comparing the entry (door) against the case interior in both horizontal orientations, which tells an agent this is a fit-check tool. However, it never states what is being checked — an item's fit through a door aperture — and the following fragments ('Small display cabinet aperture', 'Hinge clearance at the opening (mm)') read as headings rather than part of a definition. Purpose is inferable but not stated cleanly.

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 when-to-use guidance, no prerequisites, and no mention of when a different tool (e.g. a carry-case or bin-opening fit check among the siblings) would be the right choice. The only conditional hint is 'in both allowed horizontal orientations', which is about internal behavior rather than tool selection.

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.