Skip to main content
Glama

The Doll Scout Home Tools

Check straight-in case fit · Sleeved album slot

tds_sleeved_album_slot
Read-onlyIdempotent

Compare the entry and case interior in both allowed horizontal orientations. Sleeved album slot. Extra room for sleeve edges (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>",
      "sleeveTabReserveMm": "<sleeveTabReserveMm>"
    },
    "name": "tds_sleeved_album_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
allowsTurnYes
doorWidthMmYes
itemDepthMmYes
itemWidthMmYes
doorHeightMmYes
itemHeightMmYes
insideDepthMmYes
insideWidthMmYes
insideHeightMmYes
sleeveTabReserveMmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read/compute operation, so the description does not need to restate safety. It adds useful behavior by disclosing that both permitted horizontal orientations are evaluated and that sleeve-edge allowance is included, but it says nothing about what the result looks like (pass/fail, clearances, which orientation wins) despite there being no output schema.

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?

The operative sentence is front-loaded, which is good, but it is followed by two fragments ('Sleeved album slot.' and 'Extra room for sleeve edges (mm).') that read like notes rather than prose. Nothing is padded, but the fragments do not earn their place as clearly as a single well-formed sentence would.

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 ten-parameter geometric fit computation with no output schema, so the description should explain the fit criteria and the return value. It instead provides only a one-line comparison statement plus two fragments, leaving an agent unable to predict the result format or the exact comparison logic.

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 ten required parameters, so the description must carry the semantic load. It only loosely gestures at two of them: 'both allowed horizontal orientations' relates to allowsTurn, and 'Extra room for sleeve edges (mm)' relates to sleeveTabReserveMm; the door dimensions, interior dimensions, and item dimensions are left entirely to parameter names with no explanation of how they are paired or interpreted.

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 gives a verb ('Compare') and two resources ('the entry and case interior'), and the title adds 'Check straight-in case fit', so the general intent is recoverable. However, it never states that the item's dimensions are being tested against the opening, and 'Sleeved album slot' is a label rather than a purpose statement, leaving the core operation only partly specified.

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 guidance on when to call this versus alternatives such as tds_accessory_fit_through_lip or the other fit/stocktake tools, and no preconditions or exclusions are given. The only contextual cue is the implied 'both allowed horizontal orientations' check, which is behavioral rather than usage guidance.

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.