Foobos: Boston and Denver concerts and comedy

Venues

list_venues

Read-onlyIdempotent

Venues in Boston or Denver that have upcoming shows, with show_count and public facts (address, capacity, bag_policy, MBTA in Boston). Paginated: default 20, max 50, always includes total. Use get_venue or search_shows with venue= for one room and its upcoming shows.

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_venues"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add operational context — and it does: pagination defaults, the 50 cap, and the guarantee that a total is always returned. The one gap is that it doesn't state sort order or whether the "upcoming shows" filter has a time horizon.

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?

Three tight sentences with the scope front-loaded, then pagination, then the alternative. The parenthetical fact list is dense but informative; nothing is wasted, though the return-field enumeration could be trimmed given no output schema conflict.

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?

With no output schema, the description carries the return-value burden and does so: it names the fields (show_count, address, capacity, bag_policy, MBTA), the pagination behavior, and the total. Combined with annotations covering safety, an agent has everything needed to call this correctly.

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 coverage is 100%, including detailed city semantics (Boston/Cambridge/Somerville vs. Denver/Colorado) and the limit guidance with token-cost warnings, so the schema already does the heavy lifting. The description repeats the default/max pagination numbers without adding new meaning, and it says nothing about via or offset. Baseline 3 applies.

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?

The description opens by stating exactly what is returned: venues in Boston or Denver that have upcoming shows, along with show_count and public facts. It scopes the result set (only venues with upcoming shows) and distinguishes itself from get_venue in the same breath.

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?

It explicitly routes the agent: "Use get_venue or search_shows with venue= for one room and its upcoming shows." That names the alternatives and the condition that selects them, so an agent knows this tool is for browsing many venues, not one.

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?