2b2t Atlas

get_group_builds

Read-only

Page through a group's builds in stable name/ID order. Pass offset=0 initially, then advance by the returned count until a short page. get_group supplies the total count and first 20 builds.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results, from 1 to 100. Defaults to 50.
`offset`	No	Zero-based result offset. Defaults to 0; must be non-negative.
`group_id`	Yes	Persistent numeric Atlas group ID.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Zero-based result offset. Defaults to 0; must be non-negative.",
+  "type": "integer"
+}

First observedSep 14, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already mark the tool as read-only and non-destructive. The description adds useful behavioral detail beyond that: stable ordering, offset-based pagination, and the short-page termination condition. It does not mention edge cases or rate limits, but these are not critical for a read-only paging tool.

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 contain all essential guidance with no filler. The most important instruction—offset=0 initially—is front-loaded, and the pointer to get_group is brief and 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 read-only pagination tool, everything needed to call it correctly is present: the paging algorithm, the ordering guarantee, the group_id parameter, and a pointer to get_group for total count. The presence of an output schema means return-value details do not need to be repeated in the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents limit, offset, and group_id. The description adds value by explaining the offset progression pattern ('advance by the returned count until a short page') and emphasizing stable ordering, which is directly relevant to offset-based pagination behavior.

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?

The description opens with 'Page through a group's builds', a specific verb and resource, and adds the key ordering guarantee ('stable name/ID order'). It clearly distinguishes this tool from get_group, which is described as supplying only the total count and first 20 builds.

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?

It explicitly gives the paging pattern: start with offset=0 and advance by the returned count until a short page. It also names get_group as the source for total count and initial builds, giving an agent clear guidance on when to use this tool versus a sibling.

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.