Openrouteservice

Snap

snap

Read-onlyIdempotent

"Snap coordinate to nearest road" / "find closest road to [lat,lng]" / "is there a road at this point" — snap arbitrary GPS coordinates to the nearest routable OSM road for a given profile (car / bike / foot). Use to clean noisy GPS, validate routability before calling directions, or place markers on a road network.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`radius`	No
`profile`	No
`locations`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "locations": [
+      [
+        8.681495,
+        49.41461
+      ],
+      [
+        8.687872,
+        49.420318
+      ]
+    ],
+    "profile": "driving-car",
+    "radius": 50
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Snap to road response from OpenRouteService",
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds context about profiles (car/bike/foot) and use cases. No contradictions. Describes behavioral traits beyond 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?

Extremely concise: one sentence with parenthetical alternatives and use cases. Front-loaded with key verb and resource. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations and output schema, description covers purpose, usage, key parameters, and use cases. No gaps given tool complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but description explains 'profile' parameter with examples and implies 'locations' are GPS coordinates. Output schema exists. Description adds meaning beyond bare schema.

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?

Description clearly states 'Snap coordinate to nearest road' and provides alternative phrasings. It specifies the verb (snap), resource (coordinates to road), and distinguishes from sibling tools like 'directions' and 'geocode_search'.

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?

Explicit use cases: 'clean noisy GPS, validate routability before calling directions, or place markers on a road network.' It implies when to use but does not explicitly state when not to use or provide alternative tools.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.