Skip to main content
Glama

Balanced Carton Packout

bpj_balanced_carton_packout
Read-onlyIdempotent

Use the fewest cartons within the unit limit and spread identical units as evenly as possible among those cartons.

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": {
      "units": "<units>",
      "capacity": "<capacity>"
    },
    "name": "bpj_balanced_carton_packout"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsYes
capacityYes

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 establish read-only, idempotent, non-destructive, closed-world behavior. The description adds the optimization goal of fewest cartons with even unit spread, but it does not disclose tie-breaking rules, response behavior, or edge-case handling.

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?

The definition is one front-loaded sentence with no filler. It is compact, though 'unit limit' is slightly ambiguous without further structure.

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, 0% parameter description coverage, and two required inputs, the definition should explain the return value and parameter semantics. It leaves an agent guessing about the output and edge-case behavior.

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%, and the description does not define 'units' or map 'capacity' to the phrase 'unit limit'. The schema titles provide basic meaning, but the description adds no constraints, format details, or handling for zero units or oversized 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 sentence states a specific packing objective—minimizing carton count while balancing identical units—so the purpose is discernible. It does not explicitly say it returns a packing plan/distribution or distinguish itself from similarly named carton/shipping tools, keeping it below 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 prerequisite conditions, and no named alternative. The objective alone implies the scenario but does not help an agent choose this tool over another.

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.