Foobos: Boston and Denver concerts and comedy

Free shows

shows_free

Read-onlyIdempotent

Free shows in Boston or Denver. Use this for “what’s free tonight?” or “free shows this weekend”. Returns only free listings (is_free / price 0). Default window is tonight (today + next 2 days). Pass window=weekend for Fri–Sun, window=upcoming for today onward. Paginated: default 20, max 50, always includes total. Default sort=evening. Do not call shows_tonight and filter client-side — tonight is ~174 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": "shows_free"
  }
}

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
`sort`	No	evening (default): evening + upcoming first, not brunch-first chrono. time: raw chronological. popular: editorial picks first, then evening.	evening
`limit`	No	Page size. Default 20, max 50. Do not request the full list — tonight is ~174 shows / ~36k tokens.
`venue`	No	Optional venue id, slug, or name substring.
`offset`	No	Rows to skip. Use with the returned total to page.
`window`	No	tonight (default, today+2), weekend (Fri–Sun), or upcoming (today onward).	tonight
`event_type`	No	comedy or music. Comedy is public event_type / finder ty=c, NOT a genre tag. Use for “comedy this week?”.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the read-only annotations, the description discloses the return filter (is_free / price 0), default time window, pagination defaults and caps, total in responses, and a token-cost warning. These are meaningful behavioral details for an agent deciding whether and how to call it.

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?

The description is front-loaded, tightly written, and each sentence adds operational value. The warning about shows_tonight is placed at the end as a useful guardrail without burying the main purpose.

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 an 8-parameter read-only tool with no output schema, it covers the main behavior, defaults, filtering, and pagination well. It could be more complete by mentioning venue and event_type filtering, but the schema compensates for those omissions.

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%, so the parameter descriptions already carry most of the semantic load. The tool description adds some useful framing around windows and pagination, but it repeats schema details and omits via, venue, and event_type.

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 states a specific resource (free shows), scope (Boston or Denver), and the free-only filter, which distinguishes it from generic show-listing siblings. It also explicitly warns against using shows_tonight for this purpose.

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 gives concrete user questions that should trigger the tool, explains window choices, and names an alternative tool to avoid (shows_tonight with client-side filtering). This is explicit when-to-use and when-not-to-use guidance.

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?