2b2t Atlas

get_group

Read-only

Get a known group ID with history, links, total build count and the first 20 builds. To discover its ID use search_groups. Use get_group_builds with offset for additional builds; get_location for full location details. 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 group ID.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`type`	Yes
`apiUrl`	Yes
`builds`	Yes
`status`	Yes
`aliases`	Yes
`founded`	Yes
`logoUrl`	Yes
`wikiUrl`	Yes
`highways`	Yes
`recordUrl`	No
`buildCount`	No
`discordUrl`	Yes
`websiteUrl`	Yes
`attachments`	No
`description`	Yes
`canonicalUrl`	Yes
`hasMoreBuilds`	No
`interactiveUrl`	Yes
`nextBuildOffset`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 28, 2026
- addedOutput schema / properties / highways / items / properties / recordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / recordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed1 schema field changedSep 28, 2026
- addedOutput schema / properties / builds / items / properties / recordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed3 schema fields changedSep 20, 2026
- addedOutput schema / properties / buildCount
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / hasMoreBuilds
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / nextBuildOffset
```
Added value: +{
+  "type": [
+    "integer",
+    "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 / highways / items / properties / canonicalUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / highways / items / properties / interactiveUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

First observedSep 14, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, non-destructive, closed-world), but the description adds real behavioral context they cannot: the result is capped at the first 20 builds, pagination lives in a sibling tool, and the various URL fields have distinct semantics (interactiveUrl for human citations, recordUrl as a stable provenance alias with a permanent 301, apiUrl/JSONL for JSON). That is substantive disclosure beyond the structured fields.

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 its distinguishing scope are front-loaded in the first sentence, and every following sentence carries routing or field-semantics information. It is dense rather than padded, though the URL-alias sentences are tightly packed and could read more cleanly.

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 documentation is not required, yet the description still calls out the 20-build truncation and the meaning of each URL field, which are the details most likely to trip up an agent. Combined with explicit sibling routing, nothing needed 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?

Only one parameter and schema description coverage is 100% ('Persistent numeric Atlas group ID'), so the schema already carries the semantics. The description mentions 'known group ID' but adds no format, range, or lookup guidance beyond the schema. 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 a known group ID') and enumerates what comes back: history, links, total build count, and the first 20 builds. The phrase 'known group ID' plus the explicit routing to search_groups makes it clearly distinguishable from the search sibling.

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 when-to-use routing: search_groups to discover the ID, get_group_builds with offset for more builds, get_location for full location details. Each alternative is named with the condition that selects it, leaving nothing to inference.

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.