GeoSpark

Driving route

route

Read-onlyIdempotent

Driving route between two points (OSRM over OpenStreetMap): line geometry, distance in metres and duration in seconds.

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": {
      "from_latitude": "<from_latitude>",
      "from_longitude": "<from_longitude>",
      "to_latitude": "<to_latitude>",
      "to_longitude": "<to_longitude>"
    },
    "name": "route"
  }
}

Input Schema

Name	Required	Description
`to_latitude`	Yes	Latitude in degrees (WGS84)
`to_longitude`	Yes	Longitude in degrees (WGS84)
`from_latitude`	Yes	Latitude in degrees (WGS84)
`from_longitude`	Yes	Longitude in degrees (WGS84)

Output Schema

Name	Required	Default
`bbox`	No
`type`	No	FeatureCollection
`features`	Yes
`geospark`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, open-world). The description adds useful behavioral context by naming the OSRM/OpenStreetMap source and listing output units for distance and duration, though it does not discuss external service limits or failure behavior.

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 a single front-loaded sentence that states the operation, provider, and key outputs without filler. Every clause contributes useful information.

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?

Given the simple four-coordinate schema, full schema coverage, annotations, and an output schema, the definition is nearly complete. It names the external routing provider and output units, though it could mention alternatives or exclusions for full contextual fit.

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 four coordinate parameters are already fully documented with types, ranges, and WGS84 semantics. The description adds no parameter-specific meaning beyond the schema baseline.

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 states a specific verb and resource: 'Driving route between two points', and specifies the provider and returned outputs. It is clear what the tool does, but it does not explicitly differentiate itself from siblings like calculate_distance or travel_time_matrix.

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 only implied by the phrase 'Driving route between two points'. There is no explicit guidance on when to use this tool rather than alternatives such as calculate_distance, travel_time_matrix, or isochrone.

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

All GeoSpark 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.