Skip to main content
Glama

Find local events on Suumer

find_events
Read-onlyIdempotent

Things to do on one day near one US town (trivia, live music, karaoke, comedy, games, markets, talks and more), each checked against the page it came from. Give the town the person asked about ("Denver, CO", "Tampa, FL" or "Sacramento, CA") or a 5-digit ZIP, a date, and optionally a kind of event. With no town, the rough town the app shares is used, if it shares one. Read-only: it changes nothing. US events only, at most 25 per call, soonest first. Each result has its own Suumer page to cite (suumerPage), and the original source page when we can show it.

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

Input Schema

NameRequiredDescriptionDefault
dateNoThe day, written YYYY-MM-DD. Leave it out for today in that town.
kindNoKind of event. Leave it out (or "all") for everything. live_music covers concerts, bands, orchestras and choirs.
townNoThe US town and state the person asked about, like "Denver, CO", "Tampa, FL" or "Sacramento, CA", or a 5-digit ZIP code. Leave it out to use the rough town the app shares.

Output Schema

NameRequiredDescriptionDefault
dateYes
kindYes
townYes
totalYes
eventsYes
moreUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Kind of event. Leave it out (or \"all\") for everything."New value: +"Kind of event. Leave it out (or \"all\") for everything. live_music covers concerts, bands, orchestras and choirs."
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "all",
      -  "trivia",
      -  "karaoke",
      -  "music",
      -  "live_music",
      -  "dj_set",
      -  "local_band",
      -  "singer_songwriter",
      -  "music_jam",
      -  "drum_circle",
      -  "percussion_playground",
      -  "family_concert",
      -  "open_mic",
      -  "cultural_showcase",
      -  "film_concert",
      -  "music_talk",
      -  "music_learning",
      -  "darts",
      -  "pool",
      -  "games",
      -  "social_game",
      -  "puzzle_games",
      -  "robot_games",
      -  "mixed_games",
      -  "learning_games",
      -  "building_play",
      -  "board_games",
      -  "mahjong",
      -  "chess",
      -  "card_games",
      -  "bingo",
      -  "loteria",
      -  "video_games",
      -  "video_game_tournament",
      -  "accessible_games",
      -  "tabletop_roleplaying",
      -  "food_drink",
      -  "food_tasting",
      -  "food_skills",
      -  "sports_fitness",
      -  "road_race",
      -  "roller_skating",
      -  "college_football",
      -  "college_volleyball",
      -  "college_soccer",
      -  "basketball_tournament",
      -  "softball_tournament",
      -  "airshow",
      -  "fan_bar",
      -  "fan_watch_party",
      -  "comedy",
      -  "stand_up_comedy",
      -  "sketch_comedy",
      -  "improv_comedy",
      -  "talks_ideas",
      -  "public_lecture",
      -  "lecture_series",
      -  "public_debate",
      -  "author_talk",
      -  "choral_music",
      -  "classical_music",
      -  "chamber_orchestra",
      -  "symphony_orchestra",
      -  "chamber_music",
      -  "theater",
      -  "high_school_play",
      -  "community_play",
      -  "community_musical",
      -  "high_school_musical",
      -  "college_play",
      -  "college_musical",
      -  "puppet_theater",
      -  "dance_performance",
      -  "film_screening",
      -  "outdoor_movie",
      -  "arts_night",
      -  "arts",
      -  "block_party",
      -  "sales",
      -  "garage_sale",
      -  "yard_sale",
      -  "flea_market",
      -  "community",
      -  "family",
      -  "pets",
      -  "general_trivia",
      -  "music_trivia",
      -  "themed_trivia",
      -  "survey_game",
      -  "jeopardy_style_trivia",
      -  "music_bingo",
      -  "game_night",
      -  "online",
      -  "dj",
      -  "dancing",
      -  "drag",
      -  "tastings",
      -  "markets",
      -  "sports",
      -  "fitness",
      -  "kids",
      -  "festivals",
      -  "film",
      -  "movie_times",
      -  "fitness_class",
      -  "market",
      -  "festival"
      -]New value: +[
      +  "all",
      +  "trivia",
      +  "karaoke",
      +  "live_music",
      +  "dj_set",
      +  "local_band",
      +  "singer_songwriter",
      +  "music_jam",
      +  "drum_circle",
      +  "percussion_playground",
      +  "family_concert",
      +  "open_mic",
      +  "cultural_showcase",
      +  "film_concert",
      +  "music_talk",
      +  "music_learning",
      +  "darts",
      +  "pool",
      +  "games",
      +  "social_game",
      +  "puzzle_games",
      +  "robot_games",
      +  "mixed_games",
      +  "learning_games",
      +  "building_play",
      +  "board_games",
      +  "mahjong",
      +  "chess",
      +  "card_games",
      +  "bingo",
      +  "loteria",
      +  "video_games",
      +  "video_game_tournament",
      +  "accessible_games",
      +  "tabletop_roleplaying",
      +  "food_drink",
      +  "food_tasting",
      +  "food_skills",
      +  "sports_fitness",
      +  "road_race",
      +  "roller_skating",
      +  "college_football",
      +  "college_volleyball",
      +  "college_soccer",
      +  "basketball_tournament",
      +  "softball_tournament",
      +  "airshow",
      +  "fan_bar",
      +  "fan_watch_party",
      +  "comedy",
      +  "stand_up_comedy",
      +  "sketch_comedy",
      +  "improv_comedy",
      +  "talks_ideas",
      +  "public_lecture",
      +  "lecture_series",
      +  "public_debate",
      +  "author_talk",
      +  "choral_music",
      +  "classical_music",
      +  "chamber_orchestra",
      +  "symphony_orchestra",
      +  "chamber_music",
      +  "theater",
      +  "high_school_play",
      +  "community_play",
      +  "community_musical",
      +  "high_school_musical",
      +  "college_play",
      +  "college_musical",
      +  "puppet_theater",
      +  "dance_performance",
      +  "film_screening",
      +  "outdoor_movie",
      +  "arts_night",
      +  "arts",
      +  "block_party",
      +  "sales",
      +  "garage_sale",
      +  "yard_sale",
      +  "flea_market",
      +  "community",
      +  "family",
      +  "pets",
      +  "general_trivia",
      +  "music_trivia",
      +  "themed_trivia",
      +  "survey_game",
      +  "jeopardy_style_trivia",
      +  "music_bingo",
      +  "game_night",
      +  "online",
      +  "dj",
      +  "dancing",
      +  "drag",
      +  "tastings",
      +  "markets",
      +  "sports",
      +  "fitness",
      +  "kids",
      +  "festivals",
      +  "film",
      +  "movie_times",
      +  "fitness_class",
      +  "market",
      +  "festival"
      +]
    • changedInput schema / properties / town / description
      Previous value: -"A US town and state, like \"Denver, CO\", \"Tampa, FL\" or \"Sacramento, CA\", or a 5-digit ZIP code."New value: +"The US town and state the person asked about, like \"Denver, CO\", \"Tampa, FL\" or \"Sacramento, CA\", or a 5-digit ZIP code. Leave it out to use the rough town the app shares."
    • removedInput schema / required
      Removed value: -[
      -  "town"
      -]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "date": {
      +      "type": "string"
      +    },
      +    "events": {
      +      "items": {
      +        "properties": {
      +          "suumerPage": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "suumerPage"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "kind": {
      +      "type": "string"
      +    },
      +    "moreUrl": {
      +      "type": "string"
      +    },
      +    "total": {
      +      "type": "integer"
      +    },
      +    "town": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "town",
      +    "date",
      +    "kind",
      +    "total",
      +    "events",
      +    "moreUrl"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / town / description
      Previous value: -"A US town and state, like \"Columbus, OH\", or a 5-digit ZIP code."New value: +"A US town and state, like \"Denver, CO\", \"Tampa, FL\" or \"Sacramento, CA\", or a 5-digit ZIP code."
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses substantive behavior: results are checked against the source page, capped at 25 per call, ordered soonest-first, and each carries a Suumer page plus an original source page for citation. These are facts an agent cannot get from the schema.

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?

The key scoping facts (one day, one US town, read-only, max 25) come first, then parameter guidance, then return-value notes. It is slightly dense with parentheticals but every clause carries information.

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?

With an output schema present, the description needn't document return shape, yet it still flags suumerPage and the source page for citation, which is useful for downstream behavior. Combined with the defaulting rules and the 25-result cap, an agent has enough to call it correctly.

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, but the description adds real meaning: default to today when date is omitted, the town format and ZIP alternative, and the clarification that live_music subsumes concerts, bands, orchestras and choirs. The enum itself is far too large to be summarized, which limits how much the description can add.

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?

The description concretely states the resource ('things to do on one day near one US town') and enumerates the event types covered, so an agent knows exactly what it returns. It doesn't use a crisp single verb like 'find', but the title supplies that. The only sibling, report_listing_problem, is a reporting tool, so differentiation is implicit rather than stated.

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

Usage Guidelines4/5

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

It tells the agent what to supply (town, date, optional kind), what happens when no town is given (the app-shared rough town), and the geographic limit (US only). There is no explicit 'do not use this for X' exclusion, but with an unrelated sibling that gap is minor.

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