Search live events worldwide on StungEvents — concerts, festivals, sports, comedy and more. Filter by city, country, category and date. Use this to answer 'what's happening / what's on' questions for any city.
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | City name, e.g. 'London', 'Tokyo' | |
| limit | No | Max results (1-20) | |
| query | No | Free-text search (artist, event, venue) | |
| country | No | ISO-2 country code, e.g. 'GB', 'US' | |
| category | No | Event category |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It does not disclose behavioral traits beyond basic search and filtering, such as pagination, data freshness, or limits. However, for a simple search tool, the description is minimally adequate.
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 sentences with no wasted words. First sentence defines action and scope, second gives use case. Highly efficient and front-loaded.
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?
Covers search scope, event types, and filters. Lacks mention of result format, defaults (though limit param has default), or behavior if no params given. Minor gap with 'date' filter not in schema. Good for a straightforward 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 coverage is 100%, so the schema already documents all parameters. The description adds little beyond restating filters, and it mentions 'date' as a filter, but the schema has no date parameter, which could be misleading. Baseline is 3 due to high coverage.
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?
Description explicitly states the tool searches for live events on StungEvents, lists event categories (concerts, festivals, etc.), and mentions filters. It distinguishes from sibling tools like get_event (single event) by its broad search capability. The use case 'what's happening' is clear.
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?
Description explicitly says to use for 'what's happening' questions for any city, providing clear context. It does not list alternative tools or when not to use, but sibling names imply differences (e.g., get_event for single event, demand_artist for artist demand).
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: demand_artist registers demand, demand_leaders shows leaderboard, get_event fetches details, list_news provides news, plan_my_night plans outings, search_events searches events. No overlap.
All tool names follow a verb_noun pattern (e.g., demand_artist, search_events), with minor variation like plan_my_night still adhering to the pattern. Consistent and predictable.
With 6 tools, the server is well-scoped for its purpose—enough to cover key functionalities without overwhelming or being too sparse.
Covers core event discovery, demand, details, news, and planning. Missing direct listing of venues or artists, but the set is functional for typical queries.
