Skip to main content
Glama
Sign In

Geloky Geocoding

by com.geloky
OverviewDiscussionsAdmin

Multi-stop route

route
Read-onlyIdempotent

Road route through 2 to 25 points in the given order: distance and time of every leg and the total, optionally with the route shape. Costs $0.001 per leg (N points = N-1 legs); nothing is charged if routing fails.

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": {
      "points": "<points>"
    },
    "name": "route"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsNoDistance units: miles or kilometers.mi
pointsYesStops in visiting order.
vehicleNoTravel mode. direct gives the straight-line (great-circle) distance with no travel time.auto
geometryNoRoute shape to include: none, geojson (LineString of [lon, lat]) or polyline (Google encoded, precision 5).none
priorityNoFastest or shortest road route.fast

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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, so the safety profile is covered. The description adds genuinely new operational context: a per-leg price of $0.001, the N-1 leg billing relationship, and the guarantee that failures are not charged — cost behavior an agent needs before calling a paid endpoint.

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?

Two tight sentences, both front-loaded with the most decision-relevant facts — output shape first, then cost model. No filler and no repetition of the schema.

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 no output schema, the description does the work of explaining returns: per-leg distance and time, the total, and optional route shape. Combined with full schema coverage that is nearly complete; only the failure/error surface is left implicit beyond the 'nothing is charged' note.

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% and the fields are well documented (units, points ordering, vehicle modes, geometry formats, priority). The description reinforces that points are consumed 'in the given order' and that geometry is optional, but adds no syntax or constraint detail beyond what the schema already supplies; baseline 3 applies.

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: a multi-stop road route over a bounded point list that returns per-leg and total distance/time plus optional shape. It differentiates itself from a simple pairwise 'distance' call through the '2 to 25 points' / 'every leg' framing, though it never names a sibling explicitly.

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 multi-leg scope and the 'optionally with the route shape' phrasing, but there is no explicit when-to-use or when-not-to-use rule, and no guidance on when a single-leg 'distance' call or a geocode call would be the better choice.

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

All Geloky Geocoding toolsInspect
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.

Resources