Skip to main content
Glama

BRAINIAC Route & Delivery Optimisation

Multi-day visit planning

route-optimization_multi-day-plan
Read-onlyIdempotent

Assign recurring visits across a horizon with frequency and spacing rules, then route each day. Price $0.05 USDC. POST /api/v1/route-optimization/multi-day-plan. 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": {
      "horizonDays": "<horizonDays>",
      "stops": "<stops>",
      "depot": "<depot>"
    },
    "name": "route-optimization_multi-day-plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
depotYesdepot, object. Required.
stopsYesstops, array. Required.
matrixNomatrix, object. Optional.
horizonDaysYeshorizonDays, array. Required.
timeLimitMsNotimeLimitMs, integer, from 1 to 25000. Optional.
capacityPerDayNocapacityPerDay, value. Optional.
vehiclesPerDayNovehiclesPerDay, integer, from 1 to 100. Optional.
matrixFromPointsNomatrixFromPoints, string, one of euclidean, haversine. Optional.

Output Schema

NameRequiredDescriptionDefault
daysNodays. Array.
sourcesNosources. Array.
unassignedNounassigned. Array.
limitationsNolimitations. Array.
visitPatternsNovisitPatterns. 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 declare readOnly, idempotent, non-destructive and openWorld, so the bar is lower. The description adds genuinely new behavior no structured field conveys: a $0.05 USDC price, and that an unpaid call returns x402 payment terms without executing — critical context for avoiding a silent no-op.

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 the functional summary front-loaded, followed by price and the payment failure mode. The raw POST path is arguably filler for an agent but is standard for x402-style endpoints and does not obscure the substance.

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 complex 8-parameter tool with nested stop objects, an output schema is present so return values need not be described, and annotations cover the safety profile. The remaining gap is the absence of any hint about how capacityPerDay/vehiclesPerDay interact with horizonDays, which the schema labels only syntactically.

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 every field including visitsPerWeek, minGapDays, allowedDays, horizonDays, matrix and timeLimitMs is already documented. The description adds no parameter-level meaning beyond that, so 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 names a specific compound operation: assign recurring visits across a horizon honoring frequency and spacing rules, then route each day. That distinguishes it clearly from single-window siblings such as vrp-time-windows or tsp-optimize, though it never names an alternative explicitly.

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 purpose language implies when the tool applies (recurring, multi-day visit scheduling), but there is no explicit when-to-use/when-not guidance, no statement of prerequisites beyond payment, and no routing to sibling tools for simpler single-day cases.

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