2b2t Atlas

get_group

Read-only

Get one group with history, links, total build count and the first 20 builds. Use get_group_builds with offset for additional builds; get_location for full details.

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

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.5/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral detail by disclosing the returned fields and the 20-build default limit, which is not stated in the schema.

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?

Two sentences with no filler. The core behavior is front-loaded, and the alternative-tool guidance is compact and directly useful.

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?

For a simple read-only single-ID lookup with a complete input schema, output schema, and annotations, the description covers all essential call context: what is returned, the pagination boundary, and where to go for more.

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?

The only parameter, id, is already fully described in the schema as 'Persistent numeric Atlas group ID.' The description adds no additional parameter semantics, but with 100% schema coverage, the baseline of 3 is appropriate.

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?

Describes a specific operation: fetch one group with a defined set of returned data (history, links, total build count, first 20 builds). The mention of get_group_builds and get_location clearly distinguishes it from closely related sibling tools.

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?

Explicitly states when to use alternatives: get_group_builds with offset for additional builds, and get_location for full details. This gives an agent clear routing guidance rather than leaving usage 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.