Skip to main content
Glama

What's Up In: local events

by ai.whatsupin
OverviewDiscussionsAdmin

Search events across all cities

search_across_cities
Read-onlyIdempotent

Search upcoming travel-worthy events across every What's Up In city at once (Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Las Vegas, London, Mexico City, Miami, Nashville, New York, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Tokyo): where an artist, band, comedian or team is playing, which cities have a festival, conference or expo, big arena shows, races. Only events worth a trip are indexed (named performers, festivals, conferences/expos, arena shows, games, races), not every local listing; for everything in one city, use search_events with its city. Each result names its city and links to the original listing (link) and the event on that city's site (on_site). searched says which cities were included and how fresh each is.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoYYYY-MM-DD, optional
fromNoYYYY-MM-DD, default today
nearNo"lat,lon": only events within radius_km of it, with distance_km. (search_events also takes place names.) Unmapped venues are left out (place.unplaced_events).
kindsNoOnly these kinds: act = named performers; festival = festival; major = major local festival; conference = conference / expo; big_show = arena or amphitheater show; game = sports game (any level); pro_game = professional sports game (MLB, NFL, NBA, NHL, MLS, WNBA, NWSL); race = race.
limitNoDefault 50
queryNoAn artist, band, comedian, team, festival or conference name, or words to match in titles/performers/venues, e.g. 'Khruangbin', 'Oktoberfest', 'AI summit'. Optional when `kinds`, `neighborhood` or `near` is given.
citiesNoOnly these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Las Vegas, London, Mexico City, Miami, Nashville, New York, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Tokyo. Default: all.
radius_kmNoRadius for near (default 10, max 200)
trip_onlyNoOnly events worth a special trip (multi-day festivals, festivals on a city's watchlist, arena/amphitheater shows, multi-day conferences, full-distance races). Default: true when there is no query, false when searching a name.
neighborhoodNoOnly events in this neighborhood or town (whole words, e.g. 'Silver Lake', 'South End', 'Pasadena'). Events whose venue isn't mapped can't be placed and are left out; place.unplaced_events counts them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cities / description
      Previous value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Mexico City, Miami, Nashville, New York, Philadelphia, Phoenix, Pittsburgh, Portland, Tokyo. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Las Vegas, London, Mexico City, Miami, Nashville, New York, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Tokyo. Default: all."
  2. Changed1 schema field changed
    • changedInput schema / properties / cities / description
      Previous value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Mexico City, Miami, Nashville, New York, Philadelphia, Pittsburgh, Portland, Tokyo. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Mexico City, Miami, Nashville, New York, Philadelphia, Phoenix, Pittsburgh, Portland, Tokyo. Default: all."
  3. Changed1 schema field changed
    • changedInput schema / properties / cities / description
      Previous value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Mexico City, Nashville, New York, Philadelphia, Pittsburgh, Portland, Tokyo. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Mexico City, Miami, Nashville, New York, Philadelphia, Pittsburgh, Portland, Tokyo. Default: all."
  4. Changed1 schema field changed
    • changedInput schema / properties / cities / description
      Previous value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Cancún, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Mexico City, Nashville, New York, Philadelphia, Phoenix, Portland, Tokyo. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Mexico City, Nashville, New York, Philadelphia, Pittsburgh, Portland, Tokyo. Default: all."
  5. Changed1 schema field changed
    • changedInput schema / properties / cities / description
      Previous value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Dallas-Fort Worth, DC, Honolulu, New York, Philadelphia, Portland. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Cancún, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Mexico City, Nashville, New York, Philadelphia, Phoenix, Portland, Tokyo. Default: all."
  6. First observed

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that: the trip-worthiness filter that governs what is returned, the edge case that unmapped venues are excluded and counted, and the result fields (link, on_site, searched). It does not discuss pagination or ordering, but the additions are substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and information-dense, but the 28-city enumeration is duplicated verbatim from the `cities` schema field and inflates an already long single paragraph. Several clauses (indexed criteria) repeat what the `kinds`/`trip_only` schema descriptions already say, so not every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter, zero-required search tool with no output schema, the description covers scope, filtering intent, exclusions and even the shape of results (`link`, `on_site`, `searched`). Coverage is strong; only return ordering/pagination behavior is left unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter's meaning, enums, defaults and constraints are already documented in the input schema. The tool-level description mostly re-states this (e.g. the full city list and the 'only events worth a trip' framing), adding little semantics not already present per-parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (travel-worthy events) plus an explicit scope ('across every What's Up In city at once'), enumerating the city set. It also carves out what is NOT indexed (local listings), so an agent can tell it apart from search_events without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: 'for everything in one city, use search_events with its city.' It also defines the inclusion criteria (named performers, festivals, conferences/expos, arena shows, games, races), which tells the agent when this tool is the right choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All What's Up In: local events toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources