Openrouteservice

Matrix

matrix

Read-onlyIdempotent

"Distance matrix between locations" / "all-to-all travel times" / "N×M routing grid" / "drive / walk / bike times between [list]" — N×M distance and duration matrix between many points via OpenStreetMap routing. Use for traveling-salesman setup, multi-stop optimization, nearest-warehouse, fleet dispatch. Profile-aware (car / truck / bike / foot / wheelchair).

Input Schema

TableJSON Schema

Name	Required	Description
`metrics`	No	["duration","distance"]
`profile`	No
`sources`	No	Which `locations` to route FROM, as 0-based indices into that array — e.g. [0] means the first location. NOT coordinates. Omit to use every location.
`locations`	Yes
`destinations`	No	Which `locations` to route TO, as 0-based indices into that array — e.g. [1,2]. NOT coordinates. Omit to use every location.

Output Schema

TableJSON Schema

Name	Required	Description
`sources`	Yes
`metadata`	Yes
`distances`	No	Meters; only when metrics includes "distance"
`durations`	No	Seconds, sources × destinations
`destinations`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedAug 9, 2026

changedOutput schema / description

Previous value: -"Distance/duration matrix response from OpenRouteService"New value: +"Travel-time / distance matrix. `durations` and `distances` each appear only when the corresponding entry is in `metrics` (durations is the default), so neither is guaranteed."

addedOutput schema / properties

Added value: +{
+  "destinations": {
+    "items": {
+      "properties": {
+        "location": {
+          "description": "[lon, lat] snapped to the road network",
+          "items": {
+            "type": "number"
+          },
+          "type": "array"
+        },
+        "snapped_distance": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "distances": {
+    "description": "Meters; only when metrics includes \"distance\"",
+    "items": {
+      "items": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "type": "array"
+    },
+    "type": "array"
+  },
+  "durations": {
+    "description": "Seconds, sources × destinations",
+    "items": {
+      "items": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "type": "array"
+    },
+    "type": "array"
+  },
+  "metadata": {
+    "properties": {
+      "attribution": {
+        "type": "string"
+      },
+      "engine": {
+        "properties": {
+          "build_date": {
+            "type": "string"
+          },
+          "graph_date": {
+            "type": "string"
+          },
+          "osm_date": {
+            "type": "string"
+          },
+          "version": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "query": {
+        "description": "Echo of the request",
+        "type": "object"
+      },
+      "service": {
+        "type": "string"
+      },
+      "timestamp": {
+        "type": [
+          "number",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "sources": {
+    "items": {
+      "properties": {
+        "location": {
+          "description": "[lon, lat] snapped to the road network",
+          "items": {
+            "type": "number"
+          },
+          "type": "array"
+        },
+        "snapped_distance": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  }
+}

addedOutput schema / required

Added value: +[
+  "sources",
+  "destinations",
+  "metadata"
+]

Changed3 schema fields changedAug 3, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "locations": [
-      [
-        8.681495,
-        49.41461
-      ],
-      [
-        8.687872,
-        49.420318
-      ],
-      [
-        8.675444,
-        49.418892
-      ]
-    ],
-    "metrics": [
-      "duration",
-      "distance"
-    ],
-    "profile": "driving-car"
-  }
-]New value: +[
+  {
+    "locations": [
+      [
+        8.681495,
+        49.41461
+      ],
+      [
+        8.687872,
+        49.420318
+      ],
+      [
+        8.675444,
+        49.418892
+      ]
+    ],
+    "metrics": [
+      "duration",
+      "distance"
+    ],
+    "profile": "driving-car"
+  },
+  {
+    "destinations": [
+      1,
+      2
+    ],
+    "locations": [
+      [
+        8.681495,
+        49.41461
+      ],
+      [
+        8.686507,
+        49.41943
+      ],
+      [
+        8.687872,
+        49.420318
+      ]
+    ],
+    "profile": "driving-car",
+    "sources": [
+      0
+    ]
+  }
+]

addedInput schema / properties / destinations / description

Added value: +"Which `locations` to route TO, as 0-based indices into that array — e.g. [1,2]. NOT coordinates. Omit to use every location."

addedInput schema / properties / sources / description

Added value: +"Which `locations` to route FROM, as 0-based indices into that array — e.g. [0] means the first location. NOT coordinates. Omit to use every location."

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "locations": [
+      [
+        8.681495,
+        49.41461
+      ],
+      [
+        8.687872,
+        49.420318
+      ],
+      [
+        8.675444,
+        49.418892
+      ]
+    ],
+    "metrics": [
+      "duration",
+      "distance"
+    ],
+    "profile": "driving-car"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Distance/duration matrix response from OpenRouteService",
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive. The description adds behavioral context beyond that: it uses OpenStreetMap routing (external data source), is profile-aware (different travel modes), and implies scalability through 'N×M'. No contradiction with annotations.

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?

The description is compact and front-loaded: a core definition followed by use cases and profile note. The quoted aliases at the start are unconventional but serve as useful search phrases and don't add unnecessary length. Every sentence contributes meaning.

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 and strong annotations, the description covers purpose, use cases, data source (OSM), and profile modes. The N×M structure and sources/destinations are explained via schema examples. Minor gaps like coordinate ordering are left to examples but do not impair understanding.

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 60%: sources and destinations are well described ('NOT coordinates', 'Omit to use every location'), and metrics has allowed values. However, profile and locations lack schema descriptions. The tool description partially compensates by listing profile modes (car/truck/bike/foot/wheelchair) and examples imply coordinate format, but it doesn't explicitly define coordinate ordering.

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?

The description clearly defines the tool as an 'N×M distance and duration matrix between many points via OpenStreetMap routing.' The quoted aliases ('all-to-all travel times', 'drive / walk / bike times') reinforce the purpose and distinguish it from siblings like directions and isochrones.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states usage contexts: 'Use for traveling-salesman setup, multi-stop optimization, nearest-warehouse, fleet dispatch.' This gives clear when-to-use guidance, though it doesn't explicitly mention alternatives or when-not-to-use, which would earn a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Openrouteservice tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation1/5

The tool set is a chaotic mix of geographic routing, AI visibility, betting analysis, memory storage, and random utilities. Many tools overlap in purpose (e.g., multiple data lookup tools like ask_pipeworx, discover_tools, resolve_entity), and the domain is completely inconsistent, making it nearly impossible for an agent to distinguish which tool to use for a given task.

Naming Consistency1/5

Tool names follow no consistent pattern; they mix snake_case (ai_visibility_check, ask_pipeworx), camelCase (generate_llms_txt), and arbitrary verbs without a clear verb_noun structure. Some names are vague (processV2-like patterns are absent, but e.g., 'forget' is a single verb). This chaotic naming prevents an agent from predicting tool functions.

Tool Count1/5

With 27 tools covering routing, AI marketing, betting, memory, and more, the count is extremely mismatched for the server's implied purpose ('Openrouteservice'). Even ignoring the name, the number is high and the scope is far too broad, making the set unwieldy and unfocused.

Completeness1/5

No coherent domain can be inferred from the tool set; it is an arbitrary collection. The routing tools are present but overshadowed by unrelated tools. For any single domain (e.g., betting or routing), the surface is either incomplete or includes extraneous tools, leaving the set severely lacking a clear purpose.

Matrix

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources