Skip to main content
Glama

Carton uniform-orientation pack

bpj_material_shipping_carton
Read-onlyIdempotent

Compare six uniform axis-aligned orientations to find the best regular packing count inside a carton.

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": {
      "boxX": "<boxX>",
      "boxY": "<boxY>",
      "boxZ": "<boxZ>",
      "itemX": "<itemX>",
      "itemY": "<itemY>",
      "itemZ": "<itemZ>"
    },
    "name": "bpj_material_shipping_carton"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxXYes
boxYYes
boxZYes
itemXYes
itemYYes
itemZYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this read-only, idempotent, closed-world and non-destructive, so safety is covered. The description adds that six orientations are evaluated and the best count is chosen, which is useful context. It omits other meaningful behavior: whether the result is only a count or also the winning orientation, what assumptions apply (no nesting, no staggering, axis-aligned grid only), and whether item dimensions must be smaller than carton dimensions.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the terseness is partly the cause of the missing behavioral and parameter detail.

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?

With no output schema and six required numeric parameters, the description should say what comes back (a count, the winning orientation, maybe per-orientation results) and what the comparison assumes. It states neither, leaving a real gap for an agent trying to interpret the result or decide whether this tool fits a mixed-orientation packing problem.

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?

All six parameters are required and schema description coverage is 0%, so the description is expected to carry parameter meaning, yet it mentions none of them. The schema's titles do convey carton-vs-item and length/width/height roles in mm, which rescues it from a 1, but the description itself contributes nothing about dimension ordering or edge cases like items larger than the carton.

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 names a specific verb-and-resource operation: compare six uniform axis-aligned orientations to find the best regular packing count inside a carton. That is much clearer than the title alone and implicitly contrasts with a non-uniform 'balanced packout' sibling. It stops short of explicitly differentiating itself from the closest siblings, so it isn't a 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 when-to-use or when-not-to-use guidance, no mention of prerequisites, and no pointer to an alternative such as the balanced carton packout tool for non-uniform or mixed-orientation packing. The phrase 'uniform axis-aligned' hints at the applicable scenario but does not state it as 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.