Skip to main content
Glama
Sign In

2b2t Atlas

by io.github.bobymicjohn
OverviewDiscussionsAdmin

find_locations_near

Read-only

Find locations by exact planar distance; filters before limiting. For text discovery use search_locations; for nearby groups, preservation and highways together use research_area. Example: {"location_name":"Mu Megabase","radius":30000000,"limit":10,"exclude_origin":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

NameRequiredDescriptionDefault
xNoNative X coordinate; provide x/z OR location_id OR exact location_name.
zNoNative Z coordinate, paired with x.
groupNoOptional group name or alias.
limitNoMaximum results, 1 to 100.
radiusNoNative-dimension radius, 1 to 30,000,000 blocks.
dimensionNo0 Overworld, 1 Nether, 2 End. Inferred for a named location; defaults to Overworld for coordinates.
has_renderNoRequire or exclude a public render; omit for either.
location_idNoAtlas location ID as the origin; do not combine with x/z or name.
location_nameNoExact location name, case-insensitive. Ambiguous names require an ID.
exclude_originNoExclude the origin location ID when resolved by name/ID.
has_world_downloadNoRequire or exclude a downloadable WDL; omit for either.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results, 1–100."New value: +"Maximum results, 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."
    • changedOutput schema / properties / result / items / properties / y / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results, 1–100."New value: +"Maximum results, 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."
  3. Changed1 schema field changed
    • addedOutput schema / properties / result / items / properties / recordUrl
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
  4. Changed19 schema fields changed
    • changedInput schema / properties / dimension / default
      Previous value: -0New value: +null
    • changedInput schema / properties / dimension / description
      Previous value: -"Minecraft dimension: 0 Overworld, 1 Nether, or 2 End."New value: +"0 Overworld, 1 Nether, 2 End. Inferred for a named location; defaults to Overworld for coordinates."
    • changedInput schema / properties / dimension / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • addedInput schema / properties / exclude_origin
      Added value: +{
+  "default": false,
+  "description": "Exclude the origin location ID when resolved by name/ID.",
+  "type": "boolean"
+}
    • addedInput schema / properties / group
      Added value: +{
+  "default": null,
+  "description": "Optional group name or alias.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / has_render
      Added value: +{
+  "default": null,
+  "description": "Require or exclude a public render; omit for either.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
    • addedInput schema / properties / has_world_download
      Added value: +{
+  "default": null,
+  "description": "Require or exclude a downloadable WDL; omit for either.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results, from 1 to 100. Defaults to 20."New value: +"Maximum results, 1–100."
    • addedInput schema / properties / location_id
      Added value: +{
+  "default": null,
+  "description": "Atlas location ID as the origin; do not combine with x/z or name.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • addedInput schema / properties / location_name
      Added value: +{
+  "default": null,
+  "description": "Exact location name, case-insensitive. Ambiguous names require an ID.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / radius / default
      Added value: +10000
    • changedInput schema / properties / radius / description
      Previous value: -"Search radius in blocks, from 1 to 30,000,000."New value: +"Native-dimension radius, 1–30,000,000 blocks."
    • addedInput schema / properties / x / default
      Added value: +null
    • changedInput schema / properties / x / description
      Previous value: -"Native-dimension Minecraft X block coordinate."New value: +"Native X coordinate; provide x/z OR location_id OR exact location_name."
    • changedInput schema / properties / x / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • addedInput schema / properties / z / default
      Added value: +null
    • changedInput schema / properties / z / description
      Previous value: -"Native-dimension Minecraft Z block coordinate."New value: +"Native Z coordinate, paired with x."
    • changedInput schema / properties / z / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • removedInput schema / required
      Removed value: -[
-  "x",
-  "z",
-  "radius"
-]
  5. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuine behavioral trait, "filters before limiting" (limit applies post-filter), plus URL-alias semantics, but these concern output artifacts already covered by the output schema. It doesn't disclose cost, performance characteristics of a 30M-block radius scan, or ambiguity handling for origins beyond what the schema states.

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, differentiation, and example are front-loaded in that order, which is the right priority. The trailing sentences on interactiveUrl/recordUrl/apiUrl/JSONL/derivative aliases are denser and slightly off-purpose for a spatial query tool, though each carries real information.

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 11 fully documented parameters and an output schema present, the description correctly avoids restating schema detail and focuses on routing and result-URL semantics. Remaining gap is behavioral: what happens with an ambiguous or unresolvable origin, and how expensive a maximum-radius query is.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 description still adds value by demonstrating a valid parameter combination in the example and by sharpening semantics that the schema states loosely: "exact planar distance" for radius and "filters before limiting" for limit ordering.

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 ("Find locations") plus the distinguishing mechanism ("exact planar distance"), and immediately contrasts itself with search_locations and research_area. An agent can tell from the description alone that this is a spatial-radius query, not a text lookup.

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?

Explicitly routes to alternatives by condition: text discovery goes to search_locations, and grouped queries covering preservation/highways go to research_area. The inline example with a concrete radius/limit/exclude_origin combination further anchors correct invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 2b2t Atlas toolsInspect
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.

Resources