Skip to main content
Glama

The Doll Scout Home Tools

Check straight-in case fit · Crate through a tote lid

tds_transport_tote_lid_entry
Read-onlyIdempotent

Compare the entry and case interior in both allowed horizontal orientations. Crate through a tote lid. Keep-out for lid ribs (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>",
      "lidRibKeepOutMm": "<lidRibKeepOutMm>"
    },
    "name": "tds_transport_tote_lid_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
allowsTurnYes
doorWidthMmYes
itemDepthMmYes
itemWidthMmYes
doorHeightMmYes
itemHeightMmYes
insideDepthMmYes
insideWidthMmYes
insideHeightMmYes
lidRibKeepOutMmYes

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 state readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds modest domain behavior: evaluation in both permitted horizontal orientations and a lid-rib keep-out expressed in millimeters. It does not say what the comparison yields (pass/fail, limiting dimension, clearance margin) and there is no output schema to fill that gap.

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 with little filler, but the phrasing is telegraphic and disjointed: 'Crate through a tote lid.' is a bare fragment that sits awkwardly against the 'case interior' framing and is not front-loaded with a clear statement of what the tool returns.

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?

A 10-parameter geometric fit computation with no output schema demands more than three clipped sentences. Key unknowns remain: what result is produced, whether errors mean 'does not fit', how keep-out and orientation interact, and units beyond the single '(mm)' hint.

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?

Ten required parameters at 0% schema description coverage, and the description only glosses two of them: 'both allowed horizontal orientations' for allowsTurn and '(mm)' for lidRibKeepOutMm. The critical distinction between door (entry) dimensions and inside (case interior) dimensions, and how item dimensions and insideHeightMm are used, is never explained.

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 verb 'Compare' plus 'entry and case interior' signals a fit/clearance check, which is more than a restatement of the name. But the description mixes framings ('case interior', 'Crate through a tote lid') without stating the check's actual question (does it pass?) or how it differs from siblings like tds_carry_case_opening or tds_accessory_fit_through_lip.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative tool is named. 'Both allowed horizontal orientations' hints at the allowsTurn parameter, but the agent must infer when this fit check applies versus the many other case/crate tools in the sibling list.

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.