Skip to main content
Glama
Sign In

2b2t Atlas

by io.github.bobymicjohn
OverviewDiscussionsAdmin

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

NameRequiredDescriptionDefault
toYesInclusive end date in YYYY-MM-DD form.
fromYesInclusive start date in YYYY-MM-DD form.
limitNoMaximum results, from 1 to 100. Defaults to 20.
dimensionNoOptional Minecraft dimension: 0 Overworld, 1 Nether, or 2 End.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / result / items / properties / y / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
  2. Changed1 schema field changed
    • addedOutput schema / properties / result / items / properties / recordUrl
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare a safe read, but the description goes well beyond: it clarifies partial-date matching behavior, the presence of captureDatePrecision, and the output URL contract (interactiveUrl for humans, recordUrl as a permanent 301 provenance alias, apiUrl/JSONL for JSON, and the location-prefixed derivative fields). That is substantive behavior an agent could not infer from 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?

The purpose and criterion are front-loaded in the opening sentence, followed by the exclusion and then field-level guidance. It is dense but every sentence carries information; the URL-routing sentences are slightly more reference material than selection guidance, which keeps it from a 5.

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 four simple parameters and an output schema present, nothing essential is missing: the date semantics, the alternative tool, and the field-name conventions for links are all covered. The description does not waste space re-explaining return structure the output schema already defines.

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 already 100%, so the schema carries the baseline. The description still adds meaning the schema lacks: that partial year/month dates match any overlapping range and that captureDatePrecision disambiguates them, plus that the range is inclusive and historical. Dimension and limit values are left entirely to the schema.

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 first sentence names a specific verb and resource (find locations) and a precise selection criterion (an Archive warp or public render captured within inclusive historical dates). It also explicitly distinguishes itself from the sibling find_recently_added_or_modified by scope, so an agent can route between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the alternative tool for a different date concept and states the semantic trap directly ('Capture dates are not founding/destruction dates'), which is real usage guidance. It does not, however, distinguish this from the broader search_locations or geographic siblings like find_locations_near, so the routing picture is incomplete.

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