Skip to main content
Glama

BRAINIAC Route & Delivery Optimisation

Great-circle distance and duration matrix

route-optimization_distance-matrix
Read-onlyIdempotent

Build a haversine distance and estimated duration matrix from caller coordinates with optional circuity and speed. Price $0.02 USDC. POST /api/v1/route-optimization/distance-matrix. 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": {
      "locations": "<locations>"
    },
    "name": "route-optimization_distance-matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
circuityNocircuity, number, from 1 to 3. Optional.
speedKphNospeedKph, number. Optional.
speedMpsNospeedMps, number. Optional.
locationsYeslocations, array. Required.

Output Schema

NameRequiredDescriptionDefault
idsNoids. Array.
sourcesNosources. Array.
estimateNoestimate. Boolean.
distancesMNodistancesM. Array.
durationsSNodurationsS. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 open-world behavior, so the bar is lower; the description still adds real context beyond them: the $0.02 USDC price, the POST endpoint, and the exact paid-call failure mode (x402 terms returned, no computation run). It does not discuss rate limits or matrix size limits.

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 purpose, followed by price, endpoint, and payment behavior; nearly every sentence earns its place, though the endpoint path is arguably redundant for an agent that only invokes the tool.

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 no explanation, and the description covers algorithm, cost, and payment failure behavior adequately for a 4-parameter read-only tool. Only a note on coordinate volume or matrix size limits is missing.

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 coverage is 100%, so every parameter is already documented; the description only notes that circuity and speed are optional and that duration is estimated from them, which adds modest semantic value over the schema's own field descriptions.

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?

States a specific verb and resource ('Build a haversine distance and estimated duration matrix') plus the algorithm and inputs, which is enough to separate it from the route/VRP/TSP siblings without opening any 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?

Usage is implied by the resource description and the caller-coordinate input, and the payment precondition ('An unpaid call returns the x402 payment terms and does not run') is a useful operating note. However, there is no explicit when-to-use guidance or pointer to an alternative sibling for related tasks.

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