Skip to main content
Glama

BRAINIAC Route & Delivery Optimisation

Validate a multi-vehicle route plan

route-optimization_route-plan-validate
Read-onlyIdempotent

Check a manual plan for time-window, capacity, shift, precedence and duplicate/missing-stop violations. Price $0.02 USDC. POST /api/v1/route-optimization/route-plan-validate. 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": {
      "stops": "<stops>",
      "vehicles": "<vehicles>",
      "plan": "<plan>"
    },
    "name": "route-optimization_route-plan-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesplan, array. Required.
depotNodepot, object. Optional.
speedNospeed, number. Optional.
stopsYesstops, array. Required.
matrixNomatrix, object. Optional.
requestsNorequests, array. Optional.
vehiclesYesvehicles, array. Required.
requireAllStopsNorequireAllStops, boolean. Optional.
matrixFromPointsNomatrixFromPoints, string, one of euclidean, haversine. Optional.

Output Schema

NameRequiredDescriptionDefault
validNovalid. Boolean.
missingNomissing. Array.
sourcesNosources. Array.
duplicatesNoduplicates. Array.
violationsNoviolations. Array.
limitationsNolimitations. Array.

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 cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), yet the description still adds genuinely new behavior: a $0.02 USDC price and, critically, that an unpaid call returns x402 payment terms without executing. That payment-gate disclosure is not derivable from any structured field. Missing only what a failed validation returns (report vs. error).

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: what is checked first, then price, then the payment-gate caveat. Front-loaded with substance and free of filler. The raw endpoint path is the only element of marginal value to an agent.

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 nested 9-parameter validation tool with an output schema (so return shapes need not be explained), the description covers the constraint set and the payment flow adequately. It leaves undefined what a violation response looks like and what units windows/shifts use, which an agent building a plan would still have to guess.

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 each of the 9 parameters. The description's mention of 'precedence' hints at the requests pick-up/delivery pairing but adds no semantics for requireAllStops, matrixFromPoints, or supply-vs-matrix precedence. Baseline 3 applies.

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 uses a specific verb ('Check') plus a precise object ('a manual plan') and enumerates the exact violation classes tested: time-window, capacity, shift, precedence, duplicate/missing-stop. The phrase 'manual plan' implicitly separates it from the optimizer siblings (vrp-capacitated, vrp-time-windows), though it never names them.

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 reader can infer this is the tool for auditing an already-built plan rather than generating one, but there is no explicit when-to-use statement, no prerequisites, and no named alternative such as vrp-time-windows for the case where the plan is not yet built. Usage is implied, not 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