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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_group"
  }
}

Input Schema

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

Output 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.

Changed1 schema field changedOct 25, 2026
- changedOutput schema / properties / builds / items / properties / y / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
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.4/5.0

Behavior4/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, and the description adds real value beyond them: the 20-build cap, the permanent HTTP 301 behind recordUrl, and which URL field is appropriate for human links vs JSON. Minor gaps remain (build ordering, response size, auth/rate limits), which keeps it from a 5.

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?

Front-loaded with what is returned, then alternatives, then URL semantics — each sentence carries distinct operational value. The final URL-guidance run is dense and slightly run-on, but nothing is genuinely wasted.

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 structure needn't be re-explained; the description still names the key fields an agent will cite. Combined with the sibling routing and URL-format guidance, an agent has everything needed to call it correctly.

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 with 100% schema coverage ('Persistent numeric Atlas group ID'), so the schema already carries the semantics. The description adds nothing about the id beyond what the schema states; 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 (fetch a group by known ID) and immediately enumerates the payload (history, links, total build count, first 20 builds). It distinguishes itself from search_groups, get_group_builds, and get_location by name, so an agent can route 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?

Explicit routing: use search_groups to discover an ID, get_group_builds with offset for more than the first 20 builds, and get_location for full location details. When-to-use and which-alternative conditions are both spelled out.

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.