2b2t Atlas

search_highways

Read-only

Discover public, approved highways and canals by name, history, dimension or attributed group. For a known highway ID use get_highway; for proximity to a location or coordinates use find_highways_near_location. 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
`group`	No	Optional builder or maintainer group name.
`limit`	No	Maximum results, from 1 to 100. Defaults to 20.
`query`	No	Highway/canal name or words from its description. Leave empty to browse.
`dimension`	No	Optional Minecraft dimension: 0 Overworld, 1 Nether, or 2 End.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026
- addedOutput schema / properties / result / items / properties / recordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed2 schema fields changedSep 18, 2026
- addedOutput schema / properties / result / items / properties / canonicalUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / result / items / properties / interactiveUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedSep 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, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: scope is limited to public/approved highways, recordUrl permanently 301-redirects to interactive HTML, and derivatives use the location* URL variants — useful for interpreting results and picking URLs.

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

Conciseness4/5

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

Front-loaded with purpose and routing in the first sentence, then URL guidance. Dense but each clause earns its place; the final sentence about location* URL derivatives is slightly esoteric but still functional.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value documentation isn't required, and the description instead covers scope, sibling routing, and URL selection semantics. For a read-only search tool with four fully documented optional parameters, nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so the schema already documents query, group, dimension and limit with defaults and ranges. The description echoes the search facets (name, history, dimension, group) but adds no syntax, format, or interaction detail beyond what the schema provides, leaving the baseline of 3 appropriate.

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?

States a specific verb and resource ('Discover public, approved highways and canals') plus the searchable facets (name, history, dimension, group), and explicitly distinguishes itself from two siblings (get_highway for known IDs, find_highways_near_location for proximity). An agent can pick it correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names both alternatives and the exact condition that selects each one: ID lookup goes to get_highway, spatial search goes to find_highways_near_location. It also states the 'public, approved' scope, so the agent knows what the tool will and won't return.

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.