2b2t Atlas

get_highway

Read-only

Get a known public highway or canal ID with native-dimension geometry, construction metadata, credited groups, evidence notes, attachments and source links. To discover its ID use search_highways; for proximity use find_highways_near_location. Preserve original source 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
`id`	Yes	Persistent numeric Atlas highway ID.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`lit`	Yes
`name`	Yes
`slug`	Yes
`paved`	Yes
`walls`	Yes
`width`	Yes
`apiUrl`	Yes
`groups`	Yes
`height`	Yes
`mapUrl`	Yes
`points`	Yes
`status`	Yes
`yLevel`	Yes
`wikiUrl`	Yes
`category`	Yes
`enclosed`	Yes
`videoUrl`	Yes
`dimension`	Yes
`recordUrl`	No
`ringRadius`	Yes
`attachments`	No
`description`	Yes
`canonicalUrl`	No
`lengthBlocks`	Yes
`isRoofHighway`	Yes
`interactiveUrl`	No
`pavingMaterial`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 28, 2026
- addedOutput schema / properties / groups / items / properties / recordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / recordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed3 schema fields changedSep 18, 2026

addedOutput schema / properties / attachments

Added value: +{
+  "items": {
+    "properties": {
+      "apiUrl": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "attribution": {
+        "maxLength": 500,
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "caption": {
+        "maxLength": 500,
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "dateAddedUtc": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "fileName": {
+        "maxLength": 255,
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "type": "integer"
+      },
+      "locationRowid": {
+        "type": "integer"
+      },
+      "mediaType": {
+        "maxLength": 32,
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "path": {
+        "maxLength": 500,
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "sourceUrl": {
+        "maxLength": 500,
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "thumbnailPath": {
+        "maxLength": 500,
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "locationRowid",
+      "fileName",
+      "path"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / canonicalUrl

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / interactiveUrl

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 cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), so the description adds genuinely new behavioral context: preserve original source links, prefer interactiveUrl for citations, recordUrl is a stable alias with a 301 redirect, and derivatives use location-prefixed URLs. This is meaningful guidance beyond the annotations, though it leans into output-format territory that the output schema partly covers.

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?

Purpose and routing are front-loaded in the first two sentences, which is good. The trailing URL-guidance block (interactiveUrl/recordUrl/apiUrl/JSONL/derivatives) is dense and somewhat longer than strictly necessary, slightly diluting the structure.

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?

An output schema exists, so return-value explanation is not required. The description supplies the routing alternatives and link-handling semantics an agent needs to call and cite correctly, making it complete for this read-only single-param tool.

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 single required 'id' param is documented in-schema as a persistent numeric Atlas highway ID. The description does not add syntax or format detail for the parameter, 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 ('Get') and resource ('known public highway or canal ID') and enumerates the payload (geometry, metadata, credited groups, evidence notes, attachments, source links). It explicitly names the siblings search_highways and find_highways_near_location, so an agent can distinguish it without opening a schema.

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?

Gives explicit routing conditions: use search_highways to discover the ID, use find_highways_near_location for proximity. When-to-use and alternatives are fully specified rather than inferred.

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.