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

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Persistent numeric Atlas location ID.

Output Schema

TableJSON 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 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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful behavioral context about output URL forms: interactiveUrl for human links, recordUrl as a permanent 301 provenance alias, apiUrl/JSONL for JSON, and derivative URL fields. It does not discuss authentication or rate limits, but for this read-only retrieval tool the added URL semantics are substantive.

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 core purpose is front-loaded in the first sentence, followed by alternative-tool routing and URL guidance. The URL details are dense and largely earn their place, though several sentences about URL aliases could arguably be trimmed since an output schema exists.

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?

The description covers the retrieval scope, sibling alternatives, and output URL selection. With an output schema present and annotations covering safety, nothing essential for an agent to call this tool correctly 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 coverage is 100% and the single parameter is already documented as 'Persistent numeric Atlas location ID.' The description says retrieval is 'by ID' but adds no syntax, format, or constraint beyond the schema, so the baseline 3 applies.

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 and resource ('Get one canonical location by ID') and enumerates the returned data classes. It also distinguishes itself from sibling tools search_locations and research_location, so an agent can identify its role without opening other schemas.

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?

Explicitly names the alternatives for non-ID use cases: 'For name discovery use search_locations; for name resolution with nearby context use research_location.' This gives a clear when-to-use and when-to-use-otherwise boundary.

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.