Retrieve upcoming, past, or all public events for a specified username to track schedules and event history.
List events for a specific user. Returns upcoming, past, or all profile events.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Filter events by type: upcoming, past, or profile (all public events) | |
| limit | No | Maximum number of events to return | |
| username | Yes | The username to list events for |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral disclosure burden. It only restates the return categories and does not mention pagination, default type when omitted, ordering, read-only nature, or how 'profile' events are selected.
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?
Two short sentences with no filler. The action and target are front-loaded, and the return categories are listed compactly.
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?
This is adequate for a straightforward list operation: the core purpose is clear, and the schema covers parameters. However, missing default behavior for when type/limit are omitted, no pagination/ordering context, and no output schema leave moderate gaps for an agent selecting and invoking the tool.
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%, so the schema already documents all parameters. The description's mention of 'upcoming, past, or all profile events' mirrors the type enum and adds no substantial meaning beyond the schema.
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 states a specific verb and resource: 'List events for a specific user', and enumerates the three categories returned. It is clear enough to distinguish from the sibling get-event, though it does not explicitly contrast them.
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 list-events versus get-event, nor when each event type filter is appropriate. The description implies a user-scoped listing but provides no selection criteria or alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.