2b2t Atlas

get_render_metadata

Read-only

List public map-render metadata for a location, including tile templates, exact bounds, coordinate scheme, dates, provenance, and source-WDL links. 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
`location_id`	Yes	Persistent numeric Atlas location ID.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 28, 2026
- addedOutput schema / properties / result / items / properties / locationInteractiveUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / result / items / properties / locationRecordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed1 schema field changedSep 20, 2026
- addedOutput schema / properties / result / items / properties / captureDatePrecision
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed2 schema fields changedSep 20, 2026
- addedOutput schema / properties / result / items / properties / blueMapProfile
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / result / items / properties / blueMapUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed1 schema field changedSep 18, 2026
- addedOutput schema / properties / result / items / properties / locationCanonicalUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedSep 14, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world behavior. The description adds useful behavioral context beyond annotations: recordUrl has a permanent HTTP 301 redirect, interactiveUrl is preferred for human links, apiUrl/JSONL are for JSON consumption, and derivative URLs follow specific naming patterns.

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 description is front-loaded with the tool's purpose and then moves directly into output-URL semantics. Every sentence carries practical information, though the sequence of URL aliases and derivative names is somewhat dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain return structure, but it still helpfully clarifies how to choose among returned URL forms. It covers the read-only metadata purpose and annotations cover safety, leaving only sibling-tool selection as a minor gap.

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?

There is a single required parameter, location_id, and the schema description coverage is 100%, so the schema already documents its meaning as a persistent numeric Atlas location ID. The description adds only the general phrase 'for a location' and does not supplement parameter semantics beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: 'List public map-render metadata for a location,' and enumerates the fields returned (tile templates, bounds, dates, provenance, WDL links). It does not explicitly distinguish this tool from siblings such as get_location or research_location, so it falls short of a 5 under the rubric.

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

Usage Guidelines3/5

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

The description offers implied usage by stating the tool lists render metadata for a location, and it gives guidance on which returned URL fields to prefer. However, it gives no explicit when-to-use guidance or alternatives against the many sibling tools that also retrieve location data.

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.