List all groups created by your SignUpGenius account to view group IDs, titles, and member counts. Use this to retrieve group information for managing sign-ups and reports.
List groups created by the authenticated user. Returns groupid, title, and member count for each group.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Sort order for group results. |
Changes observed during successful MCP inspections.
v2.0.0Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already communicates safety, and the description adds useful behavioral context by specifying the return fields and the authenticated-user scope. It does not disclose pagination, ordering behavior, or rate limits, but for a simple read-only list tool this is acceptable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence that front-loads the action and resource, then states the return value. There is no redundant or filler content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only listing tool with one optional enum parameter, the description covers the key information: scope, returned fields, and the fact that it lists groups. It does not mention sorting behavior explicitly or pagination, but the schema covers the parameter and the tool is low-complexity, so the description is nearly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%: the sort parameter is fully documented with an enum and a description. The tool description does not add parameter detail, but the schema already carries that burden, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List'), names the resource ('groups'), and adds a clear scope ('created by the authenticated user'). It also lists the returned fields, which distinguishes it from sibling tools like list_group_members and get_group_member.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage: call this when you need an overview of the user's groups. However, it does not explicitly contrast with sibling tools such as list_group_members, get_group_member, or list_created_all, so the agent has to infer when this tool is the right choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.