Skip to main content
Glama

Uniform Pallet Layer Plan

bpj_uniform_pallet_layer_plan
Read-onlyIdempotent

Compare two uniform carton orientations per layer, without overhang or mixed patterns, and stack within the specified cargo height.

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": {
      "palletL": "<palletL>",
      "palletW": "<palletW>",
      "stack": "<stack>",
      "length": "<length>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "bpj_uniform_pallet_layer_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
stackYes
widthYes
heightYes
lengthYes
palletLYes
palletWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds genuine behavioral context beyond that: no overhang, no mixed patterns, and a hard cap at the supplied cargo stack height. What it does not disclose is what happens when no valid orientation fits, or whether the 'comparison' is returned as two candidate plans or a single chosen one.

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 dense sentence with the core action front-loaded and the constraints following in a natural order. No filler or restatement of the tool name, though the phrasing 'Compare ... and stack' mildly obscures whether the output is a comparison or a plan.

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?

This is a multi-parameter geometric computation with six required inputs and no output schema, so the description should signal the shape of the result (per-layer counts, orientation choice, total layers/units) and any infeasibility behavior. It covers the input-side constraints adequately but leaves the return contract entirely unspecified, which is a meaningful gap for a planning 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 description coverage is 0%, but every parameter carries a descriptive title ('Parcel length (cm)', 'Pallet length (cm)', 'Allowed cargo stack height (cm)'), so the effective meaning is mostly conveyed by structured data despite the metric. The description only clarifies one mapping, 'specified cargo height' to the stack parameter, and does nothing to disambiguate carton height from pallet thickness or stack allowance if those are conflated. Marginal added value over the schema.

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 computation ('compare two uniform carton orientations per layer') plus its constraints ('without overhang or mixed patterns', 'stack within the specified cargo height'), which tells an agent this is a uniform-carton layer stacking planner. It stops short of differentiating itself from related packing siblings such as bpj_balanced_carton_packout or bpj_material_layer_height_plan, so it lands at a clear-but-undifferentiated 4.

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

Usage Guidelines3/5

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

Usage context is implied through the constraints: use it when cartons are uniform in size, no overhang is acceptable, and mixed patterns are excluded. There is no explicit 'use this instead of X' routing, no statement of when the tool is inappropriate (e.g., non-uniform or mixed cartons), and no prerequisites such as whether dimensions include pallet lip clearance.

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.