Skip to main content
Glama

The Doll Scout Home Tools

Check straight-in case fit · Rigid portfolio storage

tds_portfolio_cabinet_entry
Read-onlyIdempotent

Compare the entry and case interior in both allowed horizontal orientations. Rigid portfolio storage. Binding projection reserve (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>",
      "bindingProjectionReserveMm": "<bindingProjectionReserveMm>"
    },
    "name": "tds_portfolio_cabinet_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
allowsTurnYes
doorWidthMmYes
itemDepthMmYes
itemWidthMmYes
doorHeightMmYes
itemHeightMmYes
insideDepthMmYes
insideWidthMmYes
insideHeightMmYes
bindingProjectionReserveMmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds that the fit check considers both allowed horizontal orientations and mentions a binding projection reserve, but it does not explain what result indicates fit or how clearance and reserve affect the outcome. There is no contradiction with annotations.

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

Conciseness4/5

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

The description is front-loaded into three short statements with no filler. The fragments 'Rigid portfolio storage' and 'Binding projection reserve (mm)' are terse and somewhat cryptic, but they are not excessive.

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-parameter fit-check tool with no output schema, the description should explain the fit result and key dimensional inputs. It gives orientation and reserve hints but omits most parameter semantics and return behavior, leaving the definition under-specified.

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 parameters. The description only names the binding projection reserve and hints at the turn/orientation parameter through 'both allowed horizontal orientations'; it leaves the door, interior, and item dimension parameters unexplained beyond their field names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence specifies a comparison operation between the entry opening and case interior across allowed horizontal orientations, which implies a straight-in fit check. It is more specific than the name or title alone, though it does not explicitly differentiate this tool from sibling fit-check or storage tools.

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?

The description gives no guidance on when to use this tool versus alternatives, nor does it state prerequisites or exclusions. The mention of 'both allowed horizontal orientations' is behavioral context, not 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.