2b2t Atlas

search_groups

Read-only

Discover groups by name, history or activity classification. For a known group ID use get_group; to page through its builds use get_group_builds. 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
`type`	No	Optional Atlas classification: Build, Highway, Mixed, or Other.
`limit`	No	Maximum results, from 1 to 100. Defaults to 20.
`query`	No	Group name, alias, or words from its description. Leave empty to browse.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026
- addedOutput schema / properties / result / items / properties / recordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedSep 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint=false, so the safety profile is covered. The description adds non-obvious behavioral detail about the URL fields: interactiveUrl for human citations, recordUrl as a provenance alias with a permanent 301, apiUrl/JSONL for JSON. That is real value beyond annotations, though it omits rate limits or result-shape behavior.

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 the sibling alternatives are front-loaded in the first two sentences, which is good structure. The remaining sentences are dense URL-guidance that is useful but leans toward output-format jargon rather than selection guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 values need not be explained, yet the description still clarifies the key URL fields an agent would use. Combined with clear alternatives and facet coverage, it is complete enough for correct invocation.

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%, so the schema already documents type, limit, and query with defaults and ranges. The description loosely echoes the searchable facets ('name, history or activity classification') but adds no syntax or format detail beyond the schema, 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?

The description uses a specific verb ('Discover') with the resource ('groups') and names the facets searched (name, history, activity classification). It also explicitly differentiates itself from the siblings get_group and get_group_builds, so an agent can route without opening 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?

It states when to use this tool and names the alternatives with their selecting conditions: get_group for a known group ID, get_group_builds for paging builds. This is explicit when-to-use and when-not-to-use guidance.

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.