2b2t Atlas

research_area

Read-only

Bundle nearby locations, credited groups, preservation and native-dimension highways. For only nearby locations use find_locations_near; for one named place use research_location. Use research_nocom_area for recorded NoCom storage, signs and portals. Example: {"location_name":"Block Game Jerusalem","radius":25000,"preserved_only":true}. 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.
`group`	No	Optional group name or alias for locations.
`limit`	No	Maximum locations, 1â€“100.
`radius`	No	Native-dimension radius, 1â€“30,000,000 blocks.
`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.
`preserved_only`	No	Require both a public render and downloadable WDL.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`caveat`	Yes
`origin`	Yes
`locations`	Yes
`radiusBlocks`	Yes
`nearestHighways`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 5, 2026

changedInput schema / properties / limit / description

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

changedInput schema / properties / radius / description

Previous value: -"Native-dimension radius, 1–30,000,000 blocks."New value: +"Native-dimension radius, 1â€“30,000,000 blocks."

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

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish read-only, non-destructive, non-open-world behavior, so the safety bar is met without the description. The description adds genuine non-structured context: URL alias semantics ('recordUrl is a stable provenance alias with a permanent HTTP 301 redirect'), which field to prefer for human citations versus JSON consumption, and the derivative field naming convention. It does not mention pagination or result-volume behavior, keeping it short of a 5.

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?

Purpose and sibling routing are front-loaded, then an example, then output-field guidance — a sensible ordering. The closing block of four URL-related sentences is slightly dense for what is essentially output-field selection, but each sentence carries distinct instructions.

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 clarifies how to choose among the returned URL fields. Combined with the example and the sibling routing rules, an agent has enough to invoke this 9-parameter, zero-required tool correctly; only edge behavior (what happens with ambiguous names beyond 'requires an ID') is left implicit.

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 every parameter (x/z, location_id, location_name, radius, dimension, group, limit, preserved_only) is already documented at the source. The inline example {'location_name':..., 'radius':25000, 'preserved_only':true} shows a valid combination but adds no meaning beyond what the schema states. Baseline 3 is appropriate.

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?

The verb 'Bundle' is soft, but the resource set is enumerated concretely (nearby locations, credited groups, preservation and native-dimension highways), and the description explicitly distinguishes this composite tool from find_locations_near, research_location, and research_nocom_area. An agent can pick this over its nearest siblings without opening the 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?

Three explicit routing rules are given with the condition that selects each alternative: 'For only nearby locations use find_locations_near; for one named place use research_location. Use research_nocom_area for recorded NoCom storage, signs and portals.' Nothing about tool choice is left to inference.

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.