Lists sign-ups created by the authenticated user. Filter by end date to view only active sign-ups, or see all including expired.
List sign-ups created by the authenticated user. In session mode this returns the full list (active + expired) — filter on enddate client-side if you need only active.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds useful behavioral context beyond the readOnlyHint annotation by revealing that session mode returns the full list instead of just active ones, and suggests client-side filtering. This discloses an unexpected behavior and helps the agent avoid misinterpreting the tool's name.
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 two sentences: the first states the core purpose, the second provides a necessary caveat. It is concise, front-loaded, and contains no filler.
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 description explains session mode behavior but is silent on non-session mode and how this tool differs from siblings like list_created_all and list_created_expired. Without an output schema, the return format is unspecified, leaving the agent with incomplete context for correct usage.
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 is empty (0 parameters), so the description has no parameter details to add. Per the baseline for 0 params, a score of 4 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 clearly states the tool lists sign-ups created by the authenticated user, but the 'active' aspect is ambiguous: it says 'In session mode this returns the full list (active + expired)', which contradicts the tool's name suggesting an active-only filter. It doesn't clearly distinguish from sibling tools like list_created_all or list_created_expired.
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 gives a usage hint for session mode (returns full list, filter client-side for active), but it doesn't explicitly say when to choose this tool over alternatives like list_created_all or list_created_expired. The guidance is implied rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.