2b2t Atlas

find_highways_near_location

Read-only

Find nearest points on approved highway polylines. Historical geometry, not routing or live passability. Example: {"location_name":"Block Game Jerusalem","highway_dimension":1,"limit":3}. Prefer interactiveUrl for human links and citations. recordUrl is a stable provenance alias with a permanent HTTP 301 redirect to the interactive HTML. Use apiUrl or JSONL for JSON. Derivatives use locationInteractiveUrl/locationRecordUrl.

Input Schema

TableJSON Schema

Name	Required	Description
`x`	No	Native X coordinate; provide x/z OR location_id OR exact location_name.
`z`	No	Native Z coordinate, paired with x.
`limit`	No	Maximum results, 1â€“100.
`dimension`	No	0 Overworld, 1 Nether, 2 End. Inferred for a named location; defaults to Overworld for coordinates.
`location_id`	No	Atlas location ID as the origin; do not combine with x/z or name.
`location_name`	No	Exact location name, case-insensitive. Ambiguous names require an ID.
`highway_dimension`	No	Dimension of highways to compare; omit to use origin dimension. OW/Nether use nominal 8:1 conversion; End cannot convert.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`caveat`	Yes
`origin`	Yes
`queryX`	Yes
`queryZ`	Yes
`highways`	Yes
`highwayDimension`	Yes
`skippedWithoutGeometry`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum results, 1–100."New value: +"Maximum results, 1â€“100."

Changed1 schema field changedSep 28, 2026
- addedOutput schema / properties / highways / items / properties / recordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed2 schema fields changedSep 28, 2026
- addedOutput schema / properties / origin / properties / interactiveUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / origin / properties / recordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed3 schema fields changedSep 18, 2026
- addedOutput schema / properties / highways / items / properties / canonicalUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / highways / items / properties / interactiveUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / origin / properties / canonicalUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
AddedSep 14, 2026

TDQS

A3.6/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, so the safety profile is covered. The description adds real context beyond that: the result is historical geometry rather than live routing, and recordUrl is a permanent 301 alias while interactiveUrl/apiUrl serve different consumption modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is correctly front-loaded, but the remainder is a grab-bag of URL-field advice (interactiveUrl, recordUrl, apiUrl/JSONL, locationInteractiveUrl/locationRecordUrl) that reads more like return-value documentation than invocation guidance, and the field naming is dense.

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, return values need not be re-explained, yet the description usefully covers the output URL aliases and the historical-vs-live distinction. The origin-selection alternatives and 8:1 conversion caveats are left to the schema, which is adequate but means the description alone is not fully self-contained.

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 schema already documents all seven parameters including the x/z-or-location_id-or-location_name alternatives. The worked example reinforces the location_name/highway_dimension/limit combination but adds no semantics beyond what the schema states.

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?

States a specific verb and resource ('Find nearest points on approved highway polylines') and sharpens scope with 'Historical geometry, not routing or live passability.' It does not name the relevant siblings (search_highways, get_highway), so differentiation is left implicit rather than explicit.

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?

The description distinguishes itself from routing/live-passability use cases and offers an example call, which implies when it fits. However, it gives no explicit when-to-use guidance versus search_highways, get_highway, or find_locations_near, so tool selection must be inferred.

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

All 2b2t Atlas 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.