Skip to main content
Glama

Find kids events

find_kids_events
Read-onlyIdempotent

Search upcoming family and kids events near a US city on KidsEventsThisWeek.com: library story times, museum days, camps, festivals, church kids programs and more. Useful for finding what to do with children this week, this weekend or on a given day. Takes a city and state, or a 5-digit US ZIP code (if both are given the ZIP is used; a ZIP is matched to the nearest city we cover). Returns at most 10 events, closest to the city first (0-5 miles, then 5-15, then farther) and soonest first within each distance, spread across the requested days, each with the date, start time, venue, price (free or paid), age range when known, a one-line summary and a link to the event page. Dates default to the next 7 days and the window never exceeds 31 days. Only events that start inside the window are returned.

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

Input Schema

NameRequiredDescriptionDefault
zipNo5-digit US ZIP code, for example "75034". An alternative to city and state.
cityNoCity name, for example "Plano" or "San Antonio". Give city and state, or a zip.
stateNoUS state as a two-letter code or full name, for example "TX" or "Texas".
categoryNoOptional topic filter: storytime (library story times), toddlers (ages 0-4), camps, church (church kids programs), or a holiday (halloween, christmas, easter, fourth-of-july).
end_dateNoLast day to search, YYYY-MM-DD. Default 6 days after the start date. The window is capped at 31 days.
age_yearsNoAge of the child in years. Keeps events that fit that age and events with no stated age range.
free_onlyNoSet true to return only free events.
start_dateNoFirst day to search, YYYY-MM-DD, in the city's local time. Default today.
radius_milesNoHow far from the city center to look, in miles. Default 25, maximum 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations: discloses the 10-result cap, the distance-band ordering (0-5, 5-15, farther), the soonest-first tiebreak, the day-spreading behavior, the default 7-day window with a hard 31-day cap, and that only events starting inside the window are returned. It also explains that an uncovered ZIP is matched to the nearest covered city, which is a non-obvious behavioral trait.

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?

Front-loaded with purpose and location semantics, then conditions, then return shape — every sentence carries information. It is dense but slightly overlong, and the date-window sentence partly restates what start_date/end_date descriptions already say.

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 fully compensates by enumerating each returned field (date, start time, venue, price, age range, summary, link) and the ordering. Combined with the location-precedence and date-window rules, an agent has everything needed to call it and interpret results.

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 baseline is 3, but the description adds genuine meaning the schema lacks: ZIP takes precedence when both ZIP and city/state are supplied, and ZIP is snapped to the nearest covered city. It also explains result spreading across requested days; minor params like radius_miles and free_only are left to 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?

Opens with a specific verb+resource ("Search upcoming family and kids events near a US city") and names the source site plus concrete event types, so the agent knows exactly what this retrieves. It never mentions the sibling tools (get_kids_event, list_best_around_guides), so the boundary between search and single-event lookup is left implicit.

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?

Gives clear situational framing ("what to do with children this week, this weekend or on a given day") and explains the location input precedence (ZIP over city/state), which is exactly the kind of decision guidance an agent needs. It stops short of explicit when-not-to-use guidance or naming get_kids_event as the follow-up for detail.

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