2b2t Atlas

find_locations_by_time_range

Read-only

Find locations with an Archive warp or public render captured within inclusive historical dates. For when records were added/modified in Atlas use find_recently_added_or_modified. Capture dates are not founding/destruction dates. Year/month-only dates match overlapping ranges; captureDatePrecision distinguishes them. 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
`to`	Yes	Inclusive end date in YYYY-MM-DD form.
`from`	Yes	Inclusive start date in YYYY-MM-DD form.
`limit`	No	Maximum results, from 1 to 100. Defaults to 20.
`dimension`	No	Optional Minecraft dimension: 0 Overworld, 1 Nether, or 2 End.

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

Behavior5/5

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

Annotations already cover the read-only safety profile, but the description adds substantial behavioral context beyond them: year/month-only dates match overlapping ranges and captureDatePrecision disambiguates, and recordUrl carries a permanent HTTP 301 redirect to interactive HTML. These are non-obvious behaviors an agent needs in order to interpret results correctly.

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?

Front-loaded with the core purpose and the sibling distinction, then proceeds through date semantics and URL guidance with no filler. It is dense and a little long, with the URL-variant sentences reading as secondary to the main selection decision, but every sentence carries usable information.

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 filtered-list tool with an output schema present, the description needn't explain return values, yet it usefully clarifies the URL fields agents will encounter and the date-matching edge case. Combined with annotations covering safety, nothing needed to call or interpret the tool is missing.

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 from/to/limit/dimension are already fully documented in the schema. The description adds no syntax or constraint detail for these four parameters (its detail is about output URL fields and date-matching semantics). Baseline 3 is appropriate when the schema does the heavy lifting.

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 (find) plus resource (locations) scoped to 'Archive warp or public render captured within inclusive historical dates', and explicitly names the sibling find_recently_added_or_modified as the tool for a different date concept. An agent can distinguish it from search_locations and find_recently_added_or_modified without opening 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?

Provides explicit when-to-use routing: 'For when records were added/modified in Atlas use find_recently_added_or_modified', plus a caveat that capture dates are not founding/destruction dates. It also advises which URL variant to prefer for human links vs JSON, giving concrete selection conditions rather than leaving them to inference.

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.