2b2t Atlas

search_highways

Read-only

Search public, approved 2b2t highways and canals by name, history, dimension, or attributed group.

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.

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/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 this is understood as a safe read operation. The description adds a meaningful behavioral boundary by stating only public, approved highways/canals are included, which is not present in the schema. It does not contradict any annotation and gives useful scoping beyond the structured data.

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?

A single, front-loaded sentence communicates the resource, scope, and search facets with zero filler. Every word contributes to the agent's ability to select the tool.

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 read-only search tool with fully documented optional parameters and an output schema present, the description is nearly sufficient. It conveys the resource boundary and the available search dimensions; the main missing piece is explicit routing guidance relative to sibling tools.

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 fully documents all four parameters. The description lists the high-level search criteria (name, dimension, group) but adds no format, default, or behavioral detail beyond what the schema already provides. Baseline 3 is appropriate here.

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 names a specific verb and resource: it searches public, approved 2b2t highways and canals, and it lists the searchable facets. This distinguishes it cleanly from collection-specific tools like get_highway and from spatial searches like find_highways_near_location. The only minor ambiguity is 'history', which does not map directly to a parameter, but the overall purpose is unmistakable.

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 implies this is the general metadata search for highways/canals by name, dimension, or group, but it never explicitly says when to choose this over get_highway, find_highways_near_location, or search_locations. It provides implied usage context without naming alternatives or exclusions.

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.