list_membersRetrieve the full list of members in your Shortcut workspace to manage team access and ownership.
List members in your Shortcut workspace.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "list_members"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| dry_run | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must carry the behavioral burden. The verb 'List' implies a non-mutating read operation, but the description does not disclose the effect of the dry_run parameter, pagination behavior, or any authentication/permission requirements, leaving some ambiguity.
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, front-loaded sentence with no unnecessary words. It earns its place by stating the core purpose, though it could have included a brief note about dry_run without becoming verbose.
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?
The purpose is clearly stated, but the description is incomplete because it leaves the dry_run parameter entirely unexplained and offers no guidance on return format or when to use this tool versus get_member. Given the tool's simplicity, covering the parameter would have made it 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?
The input schema has one parameter, dry_run, with no description, and the tool description does not mention it at all. Since schema description coverage is 0%, the description completely fails to add meaning to the parameter.
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 clearly uses the verb 'List' and identifies the resource as 'members' in the Shortcut workspace, making the operation unambiguous. It distinguishes from sibling get_member by listing all members rather than fetching a single one.
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 the tool is used to retrieve workspace members, but it provides no explicit when-to-use guidance or comparison with alternatives like get_member. The context is clear but no exclusions or alternative tool references are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.