Skip to main content
Glama

BRAINIAC Route & Delivery Optimisation

Vehicle routing with time windows

route-optimization_vrp-time-windows
Read-onlyIdempotent

Route stops under customer time windows, service times, driver shifts and breaks with forward time propagation. Price $0.05 USDC. POST /api/v1/route-optimization/vrp-time-windows. 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-time-windows"
  }
}

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, completion_time, vehicles. Optional.
speedMpsNospeedMps, number. Optional.
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.
timeLimitMsNotimeLimitMs. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, and the description is consistent with them while adding material context: a $0.05 USDC charge, the exact POST endpoint, and the behavior of an unpaid call (returns payment terms without executing). The 'forward time propagation' phrase signals the scheduling semantics. It omits what an infeasible-time-window result looks like, but an output schema exists, so that is forgivable.

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 and constraint scope, followed by price, endpoint and payment-failure behavior. The raw endpoint URL is borderline redundant but plausibly useful for an HTTP/x402 caller; nothing else is wasted.

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?

For a 10-parameter, deeply nested optimization tool with an output schema and full annotation coverage, the definition covers purpose, cost, transport and payment gating adequately. The remaining gap is unit/time-base semantics for the window, shift and service fields, which an agent must get right to build a valid request.

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 all 10 parameters including nested depot, stops, vehicles and matrix fields. The description adds only the conceptual framing of time propagation and shifts/breaks, with no units (seconds vs. minutes) for window, shift, service or duration fields — the one thing the schema also fails to state.

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 gives a specific verb plus resource ('Route stops') and enumerates the constraints it honors: customer time windows, service times, driver shifts and breaks, plus forward time propagation. That distinguishes it from simpler siblings like tsp-optimize or distance-matrix, though it never explicitly contrasts with vrp-capacitated or pickup-delivery, the closest overlapping siblings.

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 constraint list — an agent can infer this is the tool when stops carry time windows and vehicles have shifts/breaks. There is no explicit when-not-to-use guidance or named alternative for the capacitated-only or pickup-delivery cases. The payment precondition ('an unpaid call returns the x402 payment terms and does not run') is useful context but is a gating rule rather than routing 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.

Resources