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.

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
`attachments`	Yes
`description`	Yes
`modifiedUtc`	Yes
`canonicalUrl`	Yes
`dateAddedUtc`	Yes
`interactiveUrl`	Yes
`modifiedRecorded`	No
`dateAddedRecorded`	No

Schema Changelog

Changes observed during successful MCP inspections.

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 declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds context about what the response includes (history, groups, warps, renders, attachments, WDLs, provenance), which helps the agent anticipate the return payload. No contradictions with annotations.

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 two sentences with zero waste. The primary purpose is front-loaded in the first clause, and the alternative routing is appended in a single sentence. Every word earns its place.

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 that an output schema exists, the description need not explain return values. It clearly specifies what the tool fetches, lists the included related data, and routes to siblings for alternative use cases. For a single-parameter get-by-ID tool, nothing an agent needs to call it 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 description coverage is 100%, and the schema already explains the 'id' parameter as a 'Persistent numeric Atlas location ID.' The description only repeats 'by ID' without adding format, constraints, or usage nuance beyond the schema. This matches the baseline 3 for fully covered parameters.

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 ('Get'), a specific resource ('one canonical location by ID'), and enumerates the data scope (history, groups, warps, renders, attachments, WDLs, provenance). It distinguishes itself from siblings by explicitly naming search_locations and research_location as alternatives, making the tool's role unambiguous.

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?

The description gives explicit guidance on when NOT to use this tool: 'For name discovery use search_locations; for name resolution with nearby context use research_location.' This provides clear routing to alternatives and implies the correct use case (fetching by ID).

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.