Skip to main content
Glama

La Cartelera

Find shows by city, date or venue

find_shows
Read-onlyIdempotent

Upcoming stand-up / comedy shows. Filter by city slug (from list_cities), a window (today, weekend, upcoming = next 60 days) or an explicit date_from/date_to (YYYY-MM-DD, max 92 days), and optionally a venue slug. Dates are Mexico City time.

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": "find_shows"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity slug, e.g. cdmx, monterrey, guadalajara.
whenNoupcoming
limitNoMax rows (1-100).
venueNoVenue slug (from search or get_venue).
date_toNoYYYY-MM-DD; defaults to date_from.
date_fromNoYYYY-MM-DD; overrides when.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the bar is lower. The description nonetheless adds real operational constraints: a 92-day maximum date span, 'upcoming' meaning the next 60 days, date_from overriding when, date_to defaulting to date_from, and that dates are Mexico City time — details absent from annotations.

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?

A single dense sentence that front-loads the resource and then layers filter semantics and the timezone caveat. There is little waste, though the compression into one long sentence makes it slightly harder to scan than a short bulleted structure would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description is the only place an agent could learn what a returned row looks like (fields, ordering, pagination via limit) — and it does not say. It covers inputs and constraints thoroughly, but the return shape is left entirely to inference.

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 83% and carries most per-parameter text, yet the description still adds meaning the schema lacks: the 60-day definition of 'upcoming', the 92-day cap on explicit ranges, and the timezone in which date filters are interpreted. Minor redundancy exists where it restates the date_from-overrides-when and date_to-defaults rules already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Concrete resource plus the exact filter dimensions: 'Upcoming stand-up / comedy shows' filtered by city slug, time window, explicit dates, or venue slug. An agent can distinguish it from get_show (single show) by the plural/list framing, though the description never explicitly contrasts itself with the sibling 'search'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied rather than stated: it tells you the tool returns upcoming shows and how to source slugs ('from list_cities', 'from search or get_venue'), which is useful routing. But it never says when to prefer this over 'search', nor any exclusion such as using get_show when you already have a show id.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources