Skip to main content
Glama

BRAINIAC Route & Delivery Optimisation

Pickup and delivery routing

route-optimization_pickup-delivery
Read-onlyIdempotent

Route paired pickup-and-delivery requests with precedence, same-vehicle and capacity constraints. Price $0.05 USDC. POST /api/v1/route-optimization/pickup-delivery. 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": {
      "depot": "<depot>",
      "requests": "<requests>",
      "vehicles": "<vehicles>"
    },
    "name": "route-optimization_pickup-delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
depotYesdepot, object. Required.
speedNospeed, number. Optional.
matrixNomatrix, object. Optional.
circuityNocircuity, number, from 1 to 3. Optional.
requestsYesrequests, array. Required.
vehiclesYesvehicles, array. Required.
timeLimitMsNotimeLimitMs, integer, from 1 to 25000. Optional.
matrixFromPointsNomatrixFromPoints, string, one of euclidean, haversine. Optional.

Output Schema

NameRequiredDescriptionDefault
methodNomethod. String.
routesNoroutes. Array.
optimalNooptimal. Boolean.
sourcesNosources. Array.
estimateNoestimate. Boolean.
unassignedNounassigned. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavior an agent could not otherwise know: the $0.05 USDC price, the POST endpoint, and critically that an unpaid call returns x402 payment terms and performs no work. That payment-gate disclosure materially changes how an agent must sequence calls.

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?

Three short sentences with no filler, front-loading the capability before the cost and the payment caveat. The endpoint string is the only item of marginal value to an agent choosing a tool, but it is brief enough not to hurt.

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

Completeness5/5

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

For a complex 8-parameter, nested-object optimization tool with full schema coverage and an output schema, the description supplies exactly what the structured fields cannot: pricing, payment gating, and transport. Nothing needed to invoke it correctly appears to be missing.

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 100%, so the schema already documents depot, requests, vehicles, matrix, speed, circuity and timeLimitMs; the baseline is 3. The description adds conceptual meaning by tying 'quantity' to vehicle capacity and naming the constraint model, but contributes no syntax, format, or units detail beyond 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 verb and problem class ('Route paired pickup-and-delivery requests') plus the constraint model it enforces (precedence, same-vehicle, capacity), which is enough to distinguish it from generic VRP or TSP siblings. It stops short of explicitly naming an alternative or exclusion, so it is clear but not sibling-differentiating in the strongest sense.

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 only implied: an agent can infer this is the right tool when its loads are paired pickup/delivery with precedence requirements. No explicit when-not guidance or named alternative (e.g. vrp-capacitated, vrp-time-windows) is given, and no prerequisites beyond the payment note are 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