Skip to main content
Glama
Sign In

Listing Location Toolkit

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Drive times to places

drive_times
Read-onlyIdempotent

Drive minutes and road miles from an address to up to 20 places. Give destinations as names ("Utica, NY", "Manchester Airport") or {name, lat, lon}; leave them out to get the nearest town, nearest big cities and nearest airports automatically. OSRM router on OpenStreetMap roads, scaled to match Google Maps usual-traffic minutes. Returns rows plus ready listing lines.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "drive_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude in decimal degrees (use with lon instead of address).
lonNoLongitude in decimal degrees.
addressNoStreet address with town and ZIP or postcode, e.g. "7090 State Highway 80, Cooperstown, NY 13326" or "Ambleside LA22 9BB". Not needed when lat and lon are given.
countryNoOptional hint for the address lookup.
destinationsNoPlaces to time: strings (looked up by name, up to 6) or {name, lat, lon} objects (up to 20 in all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare read-only, idempotent, non-destructive and open-world; the description adds genuinely new behavior: the OSRM/OpenStreetMap routing source and the calibration caveat that minutes are scaled to Google's usual-traffic estimates, not live traffic. It also discloses result shape ("rows plus ready listing lines") and the 20-destination cap, which annotations do not cover.

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?

Four short sentences, front-loaded with the outcome, then input modes, then the automatic default, then the routing caveat and return shape. Every sentence carries information an agent would otherwise have to discover by trial.

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?

For a 5-parameter, all-optional tool with no output schema, the description covers input modes, defaults, caps, data source and return shape well. It leaves the actual fields of the returned "rows" and behavior on unresolvable place names unspecified, a modest gap.

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 coverage is 100%, so the schema already documents lat/lon/address/country/destinations and even the 6-string vs 20-object split. The description still adds value by stating what happens when destinations is omitted entirely, a default the schema never mentions. Minor overlap with schema text keeps it from a 5.

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?

Names a concrete verb and output ("Drive minutes and road miles") plus the exact resource and cardinality ("from an address to up to 20 places"). An agent knows precisely what this returns and that no sibling in the catalog (area_profile, crime_nearby, schools_nearby) does the same job, so no sibling differentiation is needed.

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?

Gives clear usage context: destinations may be names or objects, and omitting them triggers an automatic nearest-town / big-cities / airports mode, which is a real decision point for the caller. The stated alternative of using lat/lon instead of an address is also covered in the schema. It stops short of explicit when-not-to-use guidance or naming a competing tool, but no such tool exists here.

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

All Listing Location Toolkit 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