Skip to main content
Glama

Two-Warehouse Order Split

bpj_multi_warehouse_order_split
Read-onlyIdempotent

Allocate a shipment to the local warehouse first and the secondary warehouse next, then report unfilled units.

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>",
      "available": "<available>",
      "backup": "<backup>"
    },
    "name": "bpj_multi_warehouse_order_split"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsYes
backupYes
availableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by stating the allocation order and that unfilled units are reported, but it does not clarify the full return shape or edge-case behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence that states the allocation policy and the reported outcome without unnecessary wording.

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?

For a three-parameter computational tool with no output schema, the description gives the core allocation rule but omits return-value structure and edge-case handling. It is minimally adequate but leaves meaningful gaps that an agent would need to resolve.

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%, so the description must compensate, and it partially does by implying that local availability is consumed first, backup availability second, and unfilled units are the remainder. However, it never names the parameters, maps them explicitly to 'units', 'available', and 'backup', or explains constraints such as non-negative integer capacities.

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 states a specific action and scope: allocate a shipment across a local and secondary warehouse, then report unfilled units. It is clear what the tool does, though it does not explicitly differentiate itself from sibling tools.

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 is implied by the two-warehouse allocation behavior, but there is no explicit 'use when' guidance, no exclusions, and no named alternative tool. The local-first/secondary-second policy is operational detail rather than selection 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.