Skip to main content
Glama

What's Up In: local events

by ai.whatsupin
OverviewDiscussionsAdmin

Search events in one city

search_events
Read-onlyIdempotent

Search every upcoming event in one What's Up In city (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): music, dance, AI/tech, arts, comedy, food, sports, classes, volunteering, street fairs. Use it for "what's on in this weekend", "free comedy near " and the like. All words in query must match title/location/performers/organizer/tags. Dates are the city's local dates, YYYY-MM-DD. Each event links to its original listing (link) and carries an id for get_event.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoLatest date, YYYY-MM-DD (default: none)
cityYesWhich city (name or slug): 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. list_cities has the full list.
freeNoOnly free events
fromNoEarliest date, YYYY-MM-DD (default: today)
nearNoEvents within radius_km of a place in the city: a neighborhood, a town, a venue name, or "lat,lon". Results get distance_km, nearest first within each day.
townNoOnly events in this town or city within the metro, e.g. 'Oakland', 'Pasadena' (case-insensitive)
limitNoMax results (default 25)
queryNoFree text, e.g. 'salsa', 'hackathon', 'street fair', an artist or venue
topicNoTopic, e.g. comedy, film, food_drink, sports, talks, classes, markets, outdoors
categoryNoScored category
radius_kmNoDistance for near (default 1.5, max 50), or how far neighborhood reaches past its boundary (default 0)
neighborhoodNoOnly events in this neighborhood or town of the city, e.g. 'Capitol Hill', 'Silver Lake', 'Cambridge'. 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 / city / description
      Previous value: -"Which city (name or slug): 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. list_cities has the full list."New value: +"Which city (name or slug): 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. list_cities has the full list."
  2. Changed1 schema field changed
    • changedInput schema / properties / city / description
      Previous value: -"Which city (name or slug): 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. list_cities has the full list."New value: +"Which city (name or slug): 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. list_cities has the full list."
  3. Changed1 schema field changed
    • changedInput schema / properties / city / description
      Previous value: -"Which city (name or slug): 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. list_cities has the full list."New value: +"Which city (name or slug): 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. list_cities has the full list."
  4. Changed1 schema field changed
    • changedInput schema / properties / city / description
      Previous value: -"Which city (name or slug): 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. list_cities has the full list."New value: +"Which city (name or slug): 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. list_cities has the full list."
  5. Changed1 schema field changed
    • changedInput schema / properties / city / description
      Previous value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Dallas-Fort Worth, DC, Honolulu, New York, Philadelphia, Portland. list_cities has the full list."New value: +"Which city (name or slug): 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. list_cities has the full list."
  6. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered. The description adds genuinely non-obvious behavior: all words in `query` must match title/location/performers/organizer/tags (AND semantics), dates are city-local, and results carry `link` and `id`. Return-field and matching semantics are real value beyond annotations.

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

Conciseness4/5

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

Front-loaded with purpose and usage examples, and each sentence adds something. However, the full 28-city enumeration duplicates the `city` schema description nearly verbatim, which is wasted tokens in a description this dense.

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 12-parameter tool with no output schema, the description covers purpose, matching semantics, date conventions, and the shape of returned items (link, id). It stops short of explaining pagination/limit behavior interaction with day-grouping, but overall it is complete enough to invoke correctly.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description nonetheless adds meaning the schema lacks: the AND-matching rule for `query`, and the YYYY-MM-DD local-date convention for date params. That pushes it above baseline without being exhaustive on every one of the 12 parameters.

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 and resource ('search every upcoming event') plus an explicit scope constraint ('in one What's Up In city'). The single-city scope distinguishes it from the sibling search_across_cities without needing to open either schema.

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

Usage Guidelines4/5

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

Gives concrete usage phrasings ('what's on in <city> this weekend', 'free comedy near <neighborhood>') and points to get_event for follow-up by id. It does not explicitly say when to prefer search_across_cities or list_upcoming instead, so the alternative-routing is implied rather than stated.

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