2b2t Atlas

get_location

Read-only

Get one canonical location by ID, including history, groups, warps, renders, attachments, WDLs and provenance. For name discovery use search_locations; for name resolution with nearby context 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	Default
`id`	Yes	Persistent numeric Atlas location ID.

Output Schema

Name	Required	Description	Default
`x`	Yes
`y`	Yes
`z`	Yes
`id`	Yes
`name`	Yes
`tags`	Yes
`uuid`	Yes
`warps`	Yes
`apiUrl`	Yes
`groups`	Yes
`renders`	Yes
`wikiUrl`	Yes
`videoUrl`	Yes
`dimension`	Yes
`recordUrl`	No
`attachments`	Yes
`description`	Yes
`modifiedUtc`	Yes
`canonicalUrl`	Yes
`dateAddedUtc`	Yes
`interactiveUrl`	Yes
`modifiedRecorded`	No
`dateAddedRecorded`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026
- changedOutput schema / properties / y / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
Changed1 schema field changedSep 28, 2026
- addedOutput schema / properties / groups / items / properties / recordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed5 schema fields changedSep 28, 2026
- addedOutput schema / properties / recordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / renders / items / properties / locationInteractiveUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / renders / items / properties / locationRecordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / warps / items / properties / locationInteractiveUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / warps / items / properties / locationRecordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed2 schema fields changedSep 21, 2026
- addedOutput schema / properties / dateAddedRecorded
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / modifiedRecorded
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed2 schema fields changedSep 20, 2026
- addedOutput schema / properties / renders / items / properties / captureDatePrecision
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / warps / items / properties / captureDatePrecision
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed2 schema fields changedSep 20, 2026
- addedOutput schema / properties / renders / items / properties / blueMapProfile
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / renders / items / properties / blueMapUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed2 schema fields changedSep 18, 2026
- addedOutput schema / properties / renders / items / properties / locationCanonicalUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / warps / items / properties / locationCanonicalUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedSep 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish that this is read-only, non-destructive, and closed-world, and the description adds useful behavioral context: it returns a canonical record plus related data, and it explains URL alias semantics including a permanent 301 redirect. It does not cover pagination, response size, or error behavior, so it is strong but not fully exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and then moves cleanly to sibling routing and output-URL selection. It is dense but each sentence serves a distinct disambiguation or usage purpose.

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?

Given a one-parameter read-only tool with annotations and an output schema, the description supplies enough context: what is returned, which sibling tools cover adjacent tasks, and how to choose among interactive, record, and API URLs. No essential invocation context appears to be 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?

The single id parameter is fully documented in the schema as a 'Persistent numeric Atlas location ID,' and the description adds no syntax or format details beyond saying the lookup is by ID. With 100% schema coverage, the schema carries the parameter semantics and baseline 3 is 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: 'Get one canonical location by ID,' and lists the included data such as history, groups, warps, renders, attachments, WDLs, and provenance. It also clearly distinguishes this lookup-by-ID tool from search_locations and research_location.

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 explicitly routes the agent: use search_locations for name discovery and research_location for name resolution with nearby context. That gives clear when-to-use-this vs when-to-use-alternatives guidance.

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.