Skip to main content
Glama

BRAINIAC Route & Delivery Optimisation

ETA schedule for a fixed sequence

route-optimization_route-eta-schedule
Read-onlyIdempotent

Compute arrivals, waits, slack and overtime for a fixed stop sequence with optional return and shift end. Price $0.02 USDC. POST /api/v1/route-optimization/route-eta-schedule. 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": {
      "start": "<start>",
      "sequence": "<sequence>"
    },
    "name": "route-optimization_route-eta-schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedNospeed, number. Optional.
startYesstart, object. Required.
matrixNomatrix, object. Optional.
returnToNoreturnTo, object. Optional.
sequenceYessequence, array. Required.
shiftEndNoshiftEnd, number. Optional.
speedMpsNospeedMps, number. Optional.
matrixFromPointsNomatrixFromPoints, string, one of euclidean, haversine. Optional.

Output Schema

NameRequiredDescriptionDefault
stopsNostops. Array.
sourcesNosources. Array.
estimateNoestimate. Boolean.
overtimeNoovertime. Number.
returnTimeNoreturnTime. Number.
violationsNoviolations. Array.
limitationsNolimitations. Array.
totalDistanceNototalDistance. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds materially new behavioral facts: a concrete price ($0.02 USDC), the transport (POST endpoint), and the failure mode that an unpaid call returns x402 payment terms without executing. This is exactly the payment/auth and no-op-on-failure context an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, each earning its place: capability first, then cost, then endpoint, then the unpaid-call behavior. Nothing is repeated from the schema and the most decision-relevant content is front-loaded.

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?

With an output schema present, return values need not be described, and the description covers purpose, cost and the payment failure path for an 8-parameter nested tool. The remaining gap is unit/semantics of start.time, shiftEnd and the matrix-vs-matrixFromPoints choice, which the description leaves entirely to the schema.

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 baseline is 3. The description adds only a small amount of meaning, calling out that return and shift end are optional, but says nothing about units or interaction between matrix, matrixFromPoints, speed and speedMps, so it does not deepen parameter understanding much.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Compute arrivals, waits, slack and overtime for a fixed stop sequence" names a concrete verb and enumerates exactly what is produced, and "fixed stop sequence" implicitly separates it from the optimizing siblings (tsp-optimize, vrp-time-windows) that reorder or build sequences. An agent can tell what this returns without opening the schema.

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 phrase "fixed stop sequence" implies the precondition that the caller already has an ordered sequence rather than asking the tool to build one, which is useful implied guidance. However, no sibling is named and there is no explicit when-to-use / when-not-to-use statement, so routing versus vrp-time-windows or route-plan-validate is left to inference.

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