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

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.

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?

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds value by enumerating what the bundle aggregates (locations, credited groups, preservation, highways), which is behavioral composition info not present in the annotations. No contradiction.

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?

Three dense sentences plus a compact JSON example; purpose is front-loaded, routing follows, and the example closes with concrete usage. Every sentence earns its place with zero filler.

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?

For a 9-parameter, 0-required tool with a full output schema, the description covers the discriminating knowledge (bundle composition and sibling routing) while the schema handles parameters. An agent has everything needed to invoke it correctly.

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 baseline is 3. The embedded example adds a small usage pattern — combining location_name, radius, and preserved_only — but the description otherwise does not add parameter semantics beyond what the schema already documents.

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 ('Bundle') applied to a concrete resource set (nearby locations, credited groups, preservation, native-dimension highways) and immediately disambiguates against three siblings by name. The JSON example further concretizes the purpose by showing an actual valid call shape.

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?

Provides explicit routing rules: '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.' This is textbook when/when-not guidance with named alternatives.

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.