Foobos: Boston and Denver concerts and comedy

Staff picks

list_picks

Read-onlyIdempotent

Staff picks in Boston or Denver, each with a one-line reason. Use this for “what should I see?”, “what’s good”, “anything worth going to?”, “featured”, “date night”, “romantic”, or any public curated list. Always cite url (app deep link /e/?id=). Do not rewrite to /event/. Omit collection to list every public collection (id + title + counts) plus the default featured+popular pages. Intent → collection: date night / romantic / nice night out → date_night (do NOT use sort=popular alone); what’s good / featured → featured; big names / popular → popular; local / underrated → local_scene (or local_bands / under_the_radar); comedy night → comedy (for “comedy this week?” prefer search_shows event_type=comedy); jazz → jazz (or search genre=jazz); kids / family → tots_picks; older crowd / boomer → senior; foobos / Scott / Tot staff → foobos / scotts_picks / tots_picks; free curated → free_tonight (or shows_free); punk curated → punk (or search genre=punk); weeknight gems → weeknight_gems; St. Patrick’s → st_patricks. Not personalized For You — there is no account on this API. Each pick includes editorial why when the curated row has one so you can cite the reason. Each collection is paginated (default 20, max 50) and includes its own 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": "list_picks"
  }
}

Input Schema

Name	Required	Description	Default
`via`	No	Inbound UTM source written onto every Foobos deep link. Default muse.
`city`	No	boston (default: Boston, Cambridge, Somerville, Greater Boston) or denver (Denver, Boulder, the Colorado Front Range). Set denver for anything in Colorado.	boston
`limit`	No	Page size. Default 20, max 50. Do not request the full list — tonight is ~174 shows / ~36k tokens.
`offset`	No	Rows to skip. Use with the returned total to page.
`collection`	No	One public curated key. Omit for available catalog + featured/popular.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare this a read-only, idempotent, closed-world read; the description adds behavior beyond that: omitted collection returns the catalog plus featured/popular pages, each collection is paginated with its own total, editorial `why` fields may be present and should be cited, and the `url` deep link must be preserved rather than rewritten to /event/. That is exactly the kind of output/citation contract annotations do not convey.

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?

Purpose and the citation rule are front-loaded, and nearly every clause carries routing information. The long semicolon-chained mapping section is dense and slightly tangled where it alternates between collection keys and search fallbacks (comedy and jazz appear twice), which costs some parseability.

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 five-parameter read tool with no output schema, the definition covers selection, pagination limits, default catalog behavior, return-item shape (reason/why, url), and the no-account caveat. Nothing an agent needs in order to call it correctly and cite results is missing.

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 the baseline is 3; the description earns a bump because the `collection` enum keys are given selection meaning (which key maps to which user intent) rather than just names. It adds nothing beyond the schema for `via`, `limit`, and `offset`, whose semantics are already fully documented inline.

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 resource (public curated 'staff picks' collections) scoped to Boston or Denver, and states what each item carries ('one-line reason'). It explicitly contrasts itself with the 'For You' personalized list, so an agent can tell what this is not without consulting siblings.

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 intent→collection routing (date night → date_night, featured, popular, local_scene, tots_picks, etc.) plus negative guidance: 'do NOT use sort=popular alone' for date night, and route 'comedy this week?' to search_shows event_type=comedy and jazz/punk to search genre filters. When-to-use, when-to-defer, and which sibling to defer to are all stated.

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?