Skip to main content
Glama

Group details

get_group_info
Read-onlyIdempotent

Get a group's details and member ids, up to 200 ids per page; member_count covers the whole group and next_cursor reads the next page. list_group_plans lists the group's plans.

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": {
      "group_id": "<group_id>"
    },
    "name": "get_group_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNonext_cursor from the previous page of this tool called with the same arguments; omit for the first page.
group_idYesA group id from get_team_overview or find_athlete results.

Output Schema

NameRequiredDescriptionDefault
errorNo
groupNo
statusNo
membersNoMember user ids (or member rows).
messageNo
privacyNoPresent when the athlete's settings withhold data.
group_idNo
returnedNo
warningsNo
next_stepNoWhat can be done next, for example after a failure.
athlete_idNo
next_cursorNoReads the next page; null on the last page.
reason_codeNo
total_weeksNo
member_countNo
user_contentNoFields in this result that people wrote.
weeks_returnedNo
truncated_fieldsNoLists cut to fit one response: rows returned and total.
generated_contentNoFields in this result that NexRex's AI wrote.
session_definitionsNoSessions that several rows of this result share by session_ref.
content_block_fieldsNoColumn names of every content_blocks row, nested blocks rows included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / content_block_fields / description
      Previous value: -"Column names of every content_blocks row."New value: +"Column names of every content_blocks row, nested blocks rows included."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare it read-only, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: a hard cap of 200 member ids per page, that member_count reflects the whole group even when ids are truncated, and that next_cursor drives pagination — the main trap an agent could fall into.

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 dense sentences with zero filler. The pagination constraint, truncation semantics, and sibling routing are all front-loaded before any secondary detail.

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 no spelling out, and the description covers the one risky aspect — partial member lists and how to page through them. Only the specifics of the returned "details" fields are left implicit, which the output schema presumably covers.

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 baseline would be 3. The description earns above baseline by stating the 200-id page cap and clarifying that member_count is a whole-group total rather than a page count, plus tying cursor to next_cursor for the next page with the same arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("get a group's details and member ids") and scopes the result with pagination semantics, so it is clearly distinct from a plans-listing tool. It stops short of enumerating which "details" fields are returned, but the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a light routing hint by noting "list_group_plans lists the group's plans," which signals the alternative for plan data. There is no explicit when-not guidance or prerequisite statement, so it is clear context rather than full when/when-not/alternatives coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources