Skip to main content
Glama

BRAINIAC Route & Delivery Optimisation

Capacitated vehicle routing

route-optimization_vrp-capacitated
Read-onlyIdempotent

Assign stops to vehicles under capacity (and optional duration) limits, returning routes with loads and distances. Price $0.05 USDC. POST /api/v1/route-optimization/vrp-capacitated. 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>",
      "stops": "<stops>",
      "vehicles": "<vehicles>"
    },
    "name": "route-optimization_vrp-capacitated"
  }
}

Input Schema

NameRequiredDescriptionDefault
depotYesdepot, object. Required.
speedNospeed, number. Optional.
stopsYesstops, array. Required.
matrixNomatrix, object. Optional.
circuityNocircuity, number, from 1 to 3. Optional.
minimiseNominimise, string, one of distance, duration. Optional.
speedMpsNospeedMps, number. Optional.
vehiclesYesvehicles, array. Required.
timeLimitMsNotimeLimitMs, integer, from 1 to 25000. Optional.
matrixFromPointsNomatrixFromPoints, string, one of euclidean, haversine. Optional.
maxRouteDurationNomaxRouteDuration, value. Optional.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description goes well beyond them: it discloses the price ($0.05 USDC), the transport (POST /api/v1/route-optimization/vrp-capacitated), and critically that an unpaid call does not execute the computation. Not covered: determinism of the solver, what happens with an infeasible problem, or how timeLimitMs affects solution quality.

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?

Four short sentences, front-loaded with the capability, then cost, then endpoint, then payment failure behavior. No filler, though the raw endpoint string is arguably redundant given the name and could be trimmed.

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?

An output schema exists, so return values do not need spelling out, and the input schema is fully self-documented. For a paid computational endpoint with 11 parameters, the description covers purpose, cost, transport and the unpaid-call failure mode, leaving only sibling selection as a gap, which is scored separately.

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 every parameter including enums and nested depot/stop/vehicle objects; baseline 3 applies. The description adds only a light gloss ('capacity (and optional duration) limits' pointing at capacity and maxRouteDuration) and does not explain the matrix vs matrixFromPoints tradeoff or the minimise semantics.

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?

States a specific verb and resource ('Assign stops to vehicles') plus the defining constraint (capacity and optional duration limits) and the return content (routes with loads and distances). That is enough to distinguish it from siblings like vrp-time-windows, but the description never names a sibling or explicitly contrasts its constraint model with theirs.

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 guidance at all: nothing says when a caller should pick this over route-optimization_vrp-time-windows, route-optimization_tsp-optimize, or delivery-slot-capacity. The only conditional sentence concerns payment ('An unpaid call returns the x402 payment terms'), not tool selection.

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