Skip to main content
Glama

BRAINIAC Route & Delivery Optimisation

Vehicle loading order and 3D fit

route-optimization_vehicle-load-sequence
Read-onlyIdempotent

Order parcels last-delivered-first and run a deterministic layer first-fit packing check in a van or truck box. Price $0.03 USDC. POST /api/v1/route-optimization/vehicle-load-sequence. An unpaid call returns the x402 payment terms and does not run.

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": {
      "box": "<box>",
      "parcels": "<parcels>"
    },
    "name": "route-optimization_vehicle-load-sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxYesbox, object. Required.
unitsNounits, string, length 1 to 32. Optional.
parcelsYesparcels, array. Required.

Output Schema

NameRequiredDescriptionDefault
fitsNofits. Boolean.
methodNomethod. String.
sourcesNosources. Array.
placementsNoplacements. Array.
limitationsNolimitations. Array.
loadingOrderNoloadingOrder. Array.
volumeUtilisationNovolumeUtilisation. Number.
weightUtilisationNoweightUtilisation. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), it discloses the paid nature ($0.03 USDC), the endpoint, and critically that an unpaid call returns x402 payment terms and does not execute — a behavior an agent must know before calling. It does not, however, describe output shape or whether the maxWeight constraint is enforced in the packing check.

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?

Three short sentences, purpose front-loaded, followed by price, endpoint, and payment-gate behavior. No filler or repetition; every sentence carries operational information.

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

Completeness4/5

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

An output schema exists so return values need no explanation, and payment/auth behavior is covered. The only gap is that weight/capacity semantics (box.maxWeight) are not addressed, leaving ambiguity about whether the check is purely geometric.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description adds real meaning by tying stopIndex to last-delivered-first ordering and framing l/w/h/box/rotatable as inputs to a deterministic layer first-fit pack, which is not evident from the schema alone. The optional units parameter is left unexplained.

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 two specific operations on a specific resource: ordering parcels last-delivered-first and running a layer first-fit packing check in a van/truck box. This is clearly distinct from the sibling routing/VRP tools, so an agent can identify it without opening the schema.

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?

The description conveys what the tool does but never states when to choose it over the sibling route-planning tools or when it is not appropriate (e.g., no routing/sequencing of stops, only load order). Usage is implied by the verb phrase rather than stated.

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