Retrieve members of a SignUpGenius group using its group ID. Get basic info: name, email, and member ID.
List members of a SignUpGenius group (basic info: name, email, memberid).
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | ||
| groupId | Yes | Group ID returned by signupgenius_list_groups. |
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 annotation readOnlyHint=true already communicates that this is a safe read operation. The description adds that it returns only basic info, which is useful, but it does not mention pagination, limits, sort behavior, or any other operational caveats.
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?
One concise sentence states the action, resource, and output fields without any filler. It is front-loaded and easy to parse.
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 low-complexity read-only list tool, the description plus the groupId schema and sort enum are largely sufficient for invocation. It specifies the output fields, though it lacks details about sort semantics and sibling-tool differentiation.
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?
The schema documents groupId well but leaves sort as a bare enum with no explanation. The description does not mention sort or otherwise compensate for the 50% schema description coverage, so the agent must infer what sorting actually applies to.
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 and resource—'List members of a SignUpGenius group'—and names the returned fields (name, email, memberid). This makes the tool's purpose clear, and it is distinguishable from listing groups, though it does not explicitly contrast with the sibling 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?
No guidance is given about when to use this tool versus get_group_member or add_group_member. The schema notes that groupId comes from signupgenius_list_groups, but the description itself provides no usage context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.