Foobos: Boston and Denver concerts and comedy

Search shows

search_shows

Read-onlyIdempotent

Search every upcoming concert and comedy show in Boston or Denver. Use this for “is [artist] playing?”, “shows at [venue]”, a date or date range, a genre, or “comedy this week?”. artist / q: case- and accent-insensitive substring of billed names (Peña matches Chance Peña). venue: id, id_variant, slug, or name substring (paradise, paradise_rock_club, Sinclair). date: one YYYY-MM-DD. date_from/date_to: inclusive range. Unset dates default to upcoming (today onward). genre=/genres= is the finder mega-category (latin, jazz, rock…). Example: genre=latin + date=2026-10-15. event_type=comedy uses the public comedy field (finder ty=c / worker event_type), not genre tags. Always cite url (/e/?id=). Do not rewrite to /event/. free=true for free shows. For “what should I see?” or “date night” use list_picks instead of sort=popular. Paginated: default 20, max 50, always includes total.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_shows"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No	Alias of artist.
`via`	No	Inbound UTM source written onto every Foobos deep link. Default muse.
`area`	No	Finder WHERE pill or neighborhood (Boston: cambridge, allston_brighton, somerville…; Denver: den_downtown, den_colfax, boulder…). Aliases: neighborhood, where.
`city`	No	boston (default: Boston, Cambridge, Somerville, Greater Boston) or denver (Denver, Boulder, the Colorado Front Range). Set denver for anything in Colorado.	boston
`date`	No	Exact YYYY-MM-DD. Overrides date_from/date_to.
`free`	No	If true, only free shows (listing flag or price 0). Use for “what’s free tonight?”. Alias: is_free.
`mbta`	No	Boston only. If true, only MBTA-accessible rooms.
`sort`	No	evening (default): evening + upcoming first, not brunch-first chrono. time: raw chronological. popular: editorial picks first, then evening.	time
`genre`	No	Finder mega-category (rock, punk, pop, jazz, soul, blues, folk, electronic, hiphop, reggae, classical, latin). Alias: genres. Comedy is event_type, not a genre. Joined from finder.json `g` — do not invent tags.
`large`	No	Hint alias of min_capacity=5000.
`limit`	No	Page size. Default 20, max 50. Do not request the full list — tonight is ~174 shows / ~36k tokens.
`venue`	No	Venue id, variant, slug, or name substring.
`artist`	No	Artist substring. Alias: q. Example: Peña.
`genres`	No	Comma-separated megas. Alias of genre.
`is_new`	No	If true, only just-added (finder new).
`offset`	No	Rows to skip. Use with the returned total to page.
`date_to`	No	Inclusive range end YYYY-MM-DD.
`is_free`	No	If true, only free shows (listing flag or price 0). Use for “what’s free tonight?”. Alias: is_free.
`all_ages`	No	If true, only all-ages (a/a).
`intimate`	No	Hint alias of max_capacity=500. Unknown capacity excluded.
`date_from`	No	Inclusive range start YYYY-MM-DD.
`max_price`	No	Numeric price ceiling. Free passes; unknown price excluded.
`event_type`	No	comedy or music. Comedy is public event_type / finder ty=c, NOT a genre tag. Use for “comedy this week?”.
`max_capacity`	No	Known venues.json capacity ≤ N. intimate=true aliases max_capacity=500 (hint, not a stored flag).
`min_capacity`	No	Known venues.json capacity ≥ N. large=true aliases min_capacity=5000.
`neighborhood`	No	Alias of area.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations it discloses pagination behavior (default 20, max 50, total always returned), the default date window (upcoming when unset), and an output-hygiene rule (always cite `url` with `/e/?id=`, never rewrite to `/event/`). It stops short of covering error behavior or latency/rate characteristics, so it is strong but not exhaustive.

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 routing, then dense parameter notes and a worked example (genre=latin + date=2026-10-15) — nearly every clause carries information. It is a long unbroken block of fragments rather than scannable structure, and a couple of points (free=true, date range inclusivity) restate the schema.

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?

For a 26-parameter, all-optional tool with no output schema, the description supplies what the structured fields cannot: default date window, pagination contract with total, taxonomy coupling between genre and event_type, citation rules for the returned URL, and sibling routing. An agent has enough to call it correctly and to interpret the result without guessing.

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 coverage is 100%, so a 3 is the floor, and the description earns above it by explaining matching semantics the schema does not: artist/q is case- and accent-insensitive substring ("Peña matches Chance Peña"), venue accepts id/variant/slug/name substring, and genre is the finder mega-category while comedy is event_type rather than a tag. Some parameters (via, mbta, is_new, all_ages, max_price) are left entirely to the schema, so not every param gets added meaning.

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?

Opens with a specific verb and resource plus scope: "Search every upcoming concert and comedy show in Boston or Denver." It also enumerates the query shapes it answers (artist, venue, date, genre, comedy), which lets an agent distinguish it from siblings like shows_tonight or shows_free without reading any 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?

Provides explicit when-to-use triggers in the user's own phrasing ("is [artist] playing?", "shows at [venue]", "comedy this week?") and a named alternative with a condition: "For 'what should I see?' or 'date night' use list_picks instead of sort=popular." The exclusion is stated, not implied.

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

All Foobos: Boston and Denver concerts and comedy tools Inspect

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

Need Help?