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

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

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description adds useful return-shape context ('compact records with canonical links') plus URL semantics. However, the URL paragraph (interactiveUrl, recordUrl 301 alias, apiUrl/JSONL, locationInteractiveUrl/locationRecordUrl) is largely output-field documentation that overlaps with the output schema, so it does not add much behavioral depth beyond the structured fields.

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 is front-loaded in the first clause, followed by disambiguation and then URL guidance in a logical order. Every sentence carries information, though the tail URL/derivative sentence is dense with field names and is the weakest-value portion for tool selection.

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 seven-parameter, all-optional search tool with a 100%-covered schema, an output schema and safe read-only annotations, the description covers purpose, alternatives and link semantics. An agent has everything needed to select and 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 description coverage is 100%, so every one of the seven parameters is already documented in the schema, establishing the baseline of 3. The description restates the filter categories ('text, tags, group or preservation filters') but adds no format, syntax, or combination semantics beyond what the schema already says.

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?

Opens with a specific verb plus resource ('Discover locations') and enumerates the filter axes (text, tags, group, preservation), which maps directly onto the schema's query/type/group/has_render/has_world_download properties. It explicitly names the three sibling tools it is not, so an agent can separate it from find_locations_near, get_location and research_location without reading any 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?

Gives three concrete routing rules with the condition that selects each alternative: proximity → find_locations_near, known ID → get_location, name-based research → research_location. That is explicit when-to-use-other guidance rather than implied context.

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.