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}.

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.

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

A4.4/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 meaningful behavioral context: results are based on historical geometry, not current routing or passability, and returns points on approved polylines. This goes beyond simple annotation repetition.

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 compact and well-structured: purpose first, then key exclusions, then a concrete example. Every sentence contributes information and there is no filler or redundancy.

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 tool's complexity (7 optional parameters, dimensional conversion, coordinate/name/ID origin alternatives) and the presence of a rich input schema and output schema, the description provides the essential context: what it finds, that it is historical, and an example. It does not explicitly mention the 8:1 conversion nuance, but that is covered in the schema and is not necessary for tool selection.

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?

With 100% schema description coverage, baseline is 3. The description's example ('location_name', 'highway_dimension', 'limit') adds practical usage context beyond the schema, illustrating a valid invocation pattern and parameter combination. It does not add meaning for every parameter, but the schema already handles those.

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?

The description states a specific verb ('Find'), resource ('approved highway polylines'), and operation ('nearest points'), clearly distinguishing it from siblings like get_highway or search_highways. The line 'not routing or live passability' further sharpens the tool's purpose against potential misinterpretation.

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?

The description gives clear context on what the tool does and explicitly excludes routing/live passability, providing a when-not condition. However, it does not name alternative sibling tools or state when to prefer them, so it falls short of full alternative routing guidance.

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.