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

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 to 100.
`radius`	No	Native-dimension radius, 1 to 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

Name	Required	Description	Default
`caveat`	Yes
`origin`	Yes
`locations`	Yes
`dataSource`	No
`radiusBlocks`	Yes
`generatedAtUtc`	No
`nearestHighways`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 25, 2026

changedInput schema / properties / limit / description

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

changedInput schema / properties / radius / description

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

addedOutput schema / properties / dataSource

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / generatedAtUtc

Added value: +{
+  "format": "date-time",
+  "type": "string"
+}

changedOutput schema / properties / locations / items / properties / location / properties / y / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
changedOutput schema / properties / locations / items / properties / proximity / properties / y / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```

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.5/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, non-destructive, non-open-world operation. The description adds meaningful behavioral context beyond that by explaining URL semantics: interactiveUrl for human links/citations, recordUrl as a stable provenance alias with a permanent HTTP 301 redirect, and apiUrl/JSONL for JSON consumers. It does not contradict the annotations.

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 definition is front-loaded with the tool's purpose and its sibling alternatives, then adds a compact example and focused output-link guidance. Every sentence contributes either routing information, invocation context, or URL selection semantics, with no wasted preamble.

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?

Given the tool's complexity and nine optional parameters, the description supplies purpose, alternatives, an example, and output URL selection guidance. Because an output schema exists, it need not explain return values in full, and the remaining gaps are adequately covered by structured fields.

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%, with all nine parameters documented directly in the input schema, including origin selection rules for x/z, location_id, and location_name. The description adds only a representative example and does not supplement parameter meaning beyond what the schema already provides, so the baseline score of 3 is 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?

The description uses a specific verb, 'Bundle,' and names the concrete resources: nearby locations, credited groups, preservation, and native-dimension highways. It also explicitly distinguishes this tool from find_locations_near, research_location, and research_nocom_area, so an agent can identify its role without opening sibling schemas.

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?

It gives explicit routing guidance: use find_locations_near for only nearby locations, research_location for one named place, and research_nocom_area for NoCom storage/signs/portals. The example further clarifies a typical invocation, leaving little ambiguity about when this tool is appropriate.

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.