Skip to main content

What's Up In: local events

by ai.whatsupin

Overview Discussions Admin

Get one event

get_event

Read-onlyIdempotent

Look up one upcoming event by the id search_events or list_upcoming returned, with its source link and first_seen / last_seen / last_fetched dates.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	12-character event id
`city`	Yes	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

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."

Changed1 schema field changedOct 16, 2026

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."

Changed1 schema field changedOct 16, 2026

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."

Changed1 schema field changedOct 16, 2026

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."

Changed1 schema field changedOct 16, 2026

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."

First observedOct 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds value beyond that by disclosing the returned payload shape (source link and first_seen / last_seen / last_fetched dates), which is the main behavioral unknown for a read tool with no output schema.

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

Conciseness5/5

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

A single sentence that front-loads the lookup action and the id provenance, with the return fields tacked on economically. No filler or restatement of the name.

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 two-parameter read tool with full schema coverage and annotations, the description covers purpose, id provenance and return contents — enough to call it correctly. It omits any mention that `city` is also required and must match the event, a small gap but not blocking.

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 both parameters (including the city enum list) are already fully documented. The description only adds the provenance of `id`; it says nothing about the required `city` parameter, so it does not meaningfully exceed the schema baseline.

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?

Specific verb (look up) and resource (one upcoming event), scoped to a single record by `id`. It explicitly names search_events and list_upcoming as the producers of that id, so an agent can distinguish this from the sibling search/list tools immediately.

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?

It states the precondition for use — the id must come from search_events or list_upcoming — which effectively routes the agent: search/list first, then fetch details here. It does not spell out a when-not case (e.g., don't use for browsing), but the context is clear.

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 tools Inspect

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

Need Help?