Get the next upcoming events in a specific city, sorted by date. Great for finding what's happening soon.
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | City key (e.g. 'bengaluru', 'sf', 'mumbai') | |
| limit | No | Number of events (default 10, max 50) | |
| offset | No | Skip first N events for pagination |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that results are 'sorted by date' and limited to 'upcoming' events, providing behavioral context beyond the tool name. With no annotations, it carries the full burden, but it omits details like pagination behavior, empty result handling, or return format, leaving notable gaps.
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 concise sentences: the first states the core function and the second adds a use case. There is no redundant information and the content is front-loaded, making it efficient 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 tool with three parameters and no output schema, this description covers the basic purpose, sorting, and city requirement. However, it does not describe the expected return shape (e.g., event fields) or address edge cases like no events found. Given the absence of annotations and output schema, a more complete description would be needed to fully contextualize 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?
All three parameters have descriptions in the input schema, giving 100% schema description coverage. The tool description itself only alludes to the city parameter via 'specific city' and does not add extra meaning to limit or offset beyond what the schema already provides, matching the baseline of 3.
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 'Get' and a clear resource: 'next upcoming events in a specific city', sorted by date. This distinguishes it from siblings like list_cities (which lists cities) and search_events (which searches events), making the tool's purpose unambiguous.
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 phrase 'Great for finding what's happening soon' gives clear context for when to use this tool. However, it does not explicitly mention when not to use it or name alternatives such as search_events, so it falls short of an explicit when/when-not/alternatives guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: list_cities provides an overview of available cities, get_upcoming_events shows chronological events for a specific city, and search_events finds events by keyword across cities. There is no meaningful overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern: list_cities, get_upcoming_events, and search_events. The verbs are appropriate and the nouns clearly indicate the resource being acted on.
With only 3 tools, the server is well-scoped for event discovery. Each tool serves a distinct purpose and the count is appropriate for the domain, avoiding unnecessary bloat while providing essential functionality.
The tool set covers the core workflow of discovering events: listing cities to see what's available, getting upcoming events for a chosen city, and searching for events by topic or keyword. There are no obvious gaps for a read-only event discovery service.
