Skip to main content
Glama
Sign In

What's Up In: local events

by ai.whatsupin
OverviewDiscussionsAdmin

Get one city's coverage

get_city
Read-onlyIdempotent

Get what one What's Up In city covers: how many upcoming events it lists and for which dates, when its data was last published, how many sources feed it, and upcoming events per category, topic, neighborhood and town. Call it before searching a city to pick valid category, topic, neighborhood and town values, or to tell a user what that city covers; it returns counts only, no events (use search_events or list_upcoming for those, list_cities for every city at once). No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.

Input Schema

NameRequiredDescriptionDefault
cityYesWhich city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Paris, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list.

Output Schema

NameRequiredDescriptionDefault
mcpNo
cityYes
nameNo
siteNo
metroNo
townsNoUpcoming events per town, the busiest first (search_events `town`)
topicsNoUpcoming events per topic (search_events `topic`)
regionsNo
coverageNoCoverage and accuracy page
timezoneNo
last_dateNo
categoriesNoUpcoming events per category (search_events `category`)
first_dateNo
attributionNo
free_eventsNo
neighborhoodsNoUpcoming events per neighborhood (the `neighborhood` argument)
data_generatedNoWhen this city's data was last published
upcoming_eventsYes

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, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. 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, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Paris, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. 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, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Toronto. 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, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. 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, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City, Toronto. 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, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Toronto. 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, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. 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, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City, Toronto. 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, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. 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, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."
  6. 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, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Colorado Springs & Pueblo, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. 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, Colorado Springs & Pueblo, DC, Denver, Detroit, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."
  7. 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, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. 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, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Colorado Springs & Pueblo, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
  8. 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, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Montreal, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. 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, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
  9. 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, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. 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, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Montreal, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
  10. 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, Almaty, Anchorage, Atlanta, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. 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, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
  11. 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, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. 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, Almaty, Anchorage, Atlanta, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
  12. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral context: counts only with no event payloads, no sign-in required, and concrete rate limits (30 calls/minute, 2,500 event rows/hour). Rate limits and the no-events constraint are not derivable from any structured field.

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?

Two sentences, front-loaded with what the tool returns before routing advice and caveats. The second sentence is a dense run-on packing alternatives, exclusion, and rate limits, which slightly hurts scannability, but every clause carries information.

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

Completeness5/5

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

Output schema exists, yet the description still characterizes the shape of the response as counts-only, and it covers auth, limits, and sibling routing for a single-parameter tool. An agent has everything needed to call it correctly and interpret the result.

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% and the city parameter already lists every valid value, so the description adds no new parameter meaning beyond the schema. Baseline 3 applies since the schema does all the work here.

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?

Names a specific verb and resource ("Get what one What's Up In city covers") and enumerates exactly what comes back: event counts, date span, last-published date, source count, and per-category/topic/neighborhood/town breakdowns. It also distinguishes itself from siblings by stating it returns counts only, unlike search_events and list_upcoming.

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?

Gives explicit when-to-use ("Call it before searching a city to pick valid category, topic, neighborhood and town values, or to tell a user what that city covers") plus when-not-to and which alternative to reach for (search_events, list_upcoming, list_cities). Nothing about the routing decision is left to inference.

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