Skip to main content
Glama

The Doll Scout Home Tools

Plan packing carton quantities · Boxed plush for a move

tds_plush_moving_cartons
Read-onlyIdempotent

Calculate identical-item grid capacity and cartons needed with a reserved slot allowance. Boxed plush for a move. Open slots for unpacking access.

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>",
      "selectedAccessSlots": "<selectedAccessSlots>"
    },
    "name": "tds_plush_moving_cartons"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsToPackYes
insideWidthMmYes
packedWidthMmYes
insideHeightMmYes
insideLengthMmYes
packedHeightMmYes
packedLengthMmYes
selectedAccessSlotsYes

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?

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the agent knows this is a safe, side-effect-free computation. The description adds the meaningful behavioral element that a reserved/open slot allowance is subtracted from capacity for unpacking access, but it does not state units, rounding behavior, or what the computation returns.

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 core purpose is front-loaded in the first sentence, which is good. The two trailing sentence fragments are telegraphic and partially redundant with the first sentence, adding words without adding much specification.

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 nontrivial 8-parameter computation with no parameter documentation and no output schema, so the description carries a heavy burden. It does not explain the grid-fitting logic, the unit convention, how access slots are consumed, or what result form to expect, leaving an agent unable to predict behavior from the definition 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 semantics and largely does not. Dimension names like insideLengthMm and packedLengthMm are self-explanatory, but itemsToPack and especially selectedAccessSlots are left unexplained — the phrase "reserved slot allowance" hints at it without defining what counts as a slot or how it modifies capacity.

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 description gives a specific verb-plus-resource: "Calculate identical-item grid capacity and cartons needed," which tells an agent this is a pure planning/packing-math tool rather than a lookup or mutation. The domain phrase "Boxed plush for a move" narrows the scenario usefully, though it never explicitly contrasts with nearby siblings like tds_soft_figure_packing or tds_handoff_moving_cartons.

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 or when-not-to-use guidance and no named alternative among the many packing siblings. The fragments "Boxed plush for a move" and "Open slots for unpacking access" imply a context but do not tell an agent what condition should route it here versus to tds_packing_divider_stock or tds_handoff_moving_cartons.

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.