2b2t Atlas

search_locations

Read-only

Discover locations by text, tags, group or preservation filters; returns compact records with canonical links. For proximity use find_locations_near; for a known ID use get_location; for name-based research use research_location. 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
`type`	No	Location classification or tag, such as base, spawn, monument, or world border.
`group`	No	Builder or owning group name, including a partial name.
`limit`	No	Maximum results, from 1 to 100. Defaults to 20.
`query`	No	Words from a location name, description, tag, or Archive warp. Leave empty to browse.
`dimension`	No	Minecraft dimension: 0 Overworld, 1 Nether, or 2 End.
`has_render`	No	True to require a public map render; false to require none; omit for either.
`has_world_download`	No	True to require a publicly downloadable preserved WDL; false to require none; omit for either.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026
- addedOutput schema / properties / result / items / properties / recordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedSep 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The read-only and non-destructive annotations already cover the safety profile, so the description is not required to restate that. It adds useful behavioral context about output links: recordUrl is a stable provenance alias with a permanent HTTP 301 redirect, and JSON is available through apiUrl or JSONL. It does not discuss pagination or rate limits, but it substantially enriches the link semantics.

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?

The description is front-loaded with purpose and routing guidance, then covers link semantics compactly. It is dense but not wasteful; the final URL-derivative sentence is arguably more detail than needed for tool selection, but it remains relevant and structured.

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?

With an output schema available, the description need not explain return values in full, and it appropriately focuses on selection guidance and URL handling. Annotations cover safety, the schema covers all parameters, and the description names the most relevant alternatives, so an agent has what it needs to call this tool 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 description coverage is 100%, so all seven parameters are already documented in the input schema. The description only implies the filter categories generically and does not add syntax, format, or interaction details beyond what the schema provides, making the baseline 3 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 states a specific verb and resource: discover locations by text, tags, group, or preservation filters, and notes that it returns compact records with canonical links. It explicitly distinguishes this tool from siblings by naming find_locations_near, get_location, and research_location with the conditions that select them.

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 proximity, get_location for a known ID, and research_location for name-based research. It also tells the agent to prefer interactiveUrl for human links and apiUrl or JSONL for JSON, which clarifies intended usage beyond simple search.

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.