Skip to main content
Glama

carton-fit

Pack items into the smallest fitting carton (bounded heuristic) — Checks whether up to 50 box-shaped items (axis-aligned, 90-degree rotations, optional this-side-up lock, optional weights) fit into any of up to 20 candidate cartons, and recommends the smallest-volume carton for which a packing was found, with coordinates for every item. For shipping and fulfilment agents sizing a parcel. The packing is a greedy extreme-point HEURISTIC with a fixed step cap, not

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": {
      "items": "<items>",
      "boxes": "<boxes>"
    },
    "name": "carton-fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxesYesAt most 20. Use inner dimensions.
itemsYesAt most 50 item lines and 50 units in total (sum of qty).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the load, and it does disclose the most consequential traits: the result is a greedy extreme-point heuristic with a fixed step cap, so answers are non-optimal and bounded in effort, and rotation / this-side-up / weight constraints are all surfaced. However, the final sentence is cut off mid-clause ('not '), leaving the crucial 'not exact/optimal' caveat unfinished, and nothing is said about failure behaviour when no carton fits.

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 opening is well front-loaded, leading with the outcome ('smallest fitting carton') before the constraints. But the text is truncated mid-sentence, so the most important qualification about the heuristic is left dangling — a structural defect rather than mere verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must convey what comes back; it says a recommended carton 'with coordinates for every item' but never sketches the response shape, how 'no fit' is signalled, or the meaning of the step cap. Combined with the truncated closing sentence, the definition is serviceable but leaves real gaps for a computational-geometry tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so every field is already documented in the input schema, and the description mostly restates those limits (up to 50 box-shaped items, up to 20 candidate cartons, optional this-side-up lock, optional weights). It adds little field-level meaning beyond the schema, so the baseline of 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Pack items into the smallest fitting carton') plus the exact decision rule (smallest-volume carton for which a packing was found) and hard scale limits (≤50 items, ≤20 cartons). An agent can tell this apart from geometry siblings like platform-text-fit or appointment-fit purely from the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear context of use — 'For shipping and fulfilment agents sizing a parcel' — which tells the agent the domain and task this serves. It does not name when NOT to use it, nor point at any alternative for related sizing questions, so it stops short of full routing 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.

Resources