Skip to main content
Glama

The Doll Scout Home Tools

Plan packing carton quantities · Lidded bins grouped for transit

tds_lidded_drawer_bins_run
Read-onlyIdempotent

Calculate identical-item grid capacity and cartons needed with a reserved slot allowance. Lidded bins grouped for transit. Spaces reserved around straps.

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": {
      "insideLengthMm": "<insideLengthMm>",
      "insideWidthMm": "<insideWidthMm>",
      "insideHeightMm": "<insideHeightMm>",
      "packedLengthMm": "<packedLengthMm>",
      "packedWidthMm": "<packedWidthMm>",
      "packedHeightMm": "<packedHeightMm>",
      "itemsToPack": "<itemsToPack>",
      "strapSlots": "<strapSlots>"
    },
    "name": "tds_lidded_drawer_bins_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
strapSlotsYes
itemsToPackYes
insideWidthMmYes
packedWidthMmYes
insideHeightMmYes
insideLengthMmYes
packedHeightMmYes
packedLengthMmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, idempotent, closed-world computation, so the safety profile needs no repetition. The description does add one genuine behavioral detail beyond the annotations: capacity is reduced by a reserved slot allowance with spaces held around straps. It stops short of explaining how that allowance is computed or what the response reports, which keeps it at 3.

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 main computation is front-loaded correctly and the text is short. But the middle sentence, 'Lidded bins grouped for transit,' simply restates the title in fragmentary form and adds no information the agent can act on, so the definition is terse without being efficient.

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 tool with 8 mandatory, undocumented parameters, no output schema, and a numeric calculation whose result the agent must trust, this description is thin. It never states the units, never defines which dimensions describe the item versus the carton interior, and never characterizes the returned quantities, leaving the agent to infer call semantics from parameter names alone.

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 8 required parameters, so the description must carry the whole load and does not. It hints at itemsToPack and the inside dimensions via 'identical-item grid capacity' and gestures at strapSlots via 'spaces reserved around straps', but never explains units (mm), the crucial distinction between inside* container dimensions and packed* item dimensions, or the upper bounds.

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 gives a specific verb and resource: 'Calculate identical-item grid capacity and cartons needed.' That is a recognizable packing-math operation, distinct from names like tds_ornament_carton_run or tds_packing_divider_stock. It doesn't explicitly contrast itself with those siblings, so it lands at 4 rather than 5.

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 statement of when to choose this over sibling packing tools, no preconditions, and no notes on what inputs must be measured before calling. The opening sentence implies the scenario (planning carton counts for identical items) but gives no explicit routing guidance or exclusions.

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.