Skip to main content
Glama

events

by bot.yeehaw

find_events

Find upcoming Austin events from Yeehaw's sourced, deduplicated store. Structured filter over the events table; events more than 24h past are filtered. Every record carries a source attribution and a confidence score. Pass id to fetch one event by id; it ignores date_range and all other filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoFetch one event by id; ignores date_range and other filters when set.
limitNoMax results, default 20, clamped to 50.
queryNoFree-text keyword match against event titles.
categoryNoCategory slug (e.g. music, sports, civic).
price_maxNoMaximum ticket price in USD. price_max=0 returns only events with a known $0 price. Most events have no listed price (sparse upstream data) — for price_max>0 those are still returned and the response states how many were not price-filtered.
date_rangeNoRequired unless `id` is set. e.g. today, tonight, this_weekend, next_7_days, or an ISO date range.
neighborhoodNoAustin neighborhood slug. One of: downtown, east-austin, hyde-park, mueller, rainey-street, south-congress, the-domain, zilker. Common shorthands (east, domain, soco, rainey) are accepted.

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the transparency burden. It usefully discloses that events more than 24h past are filtered, every record has source and confidence fields, and passing id bypasses date_range and other filters. This goes beyond the basic schema and helps the agent understand edge cases.

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 compact and front-loaded, using three sentences to convey purpose, data transparency, and the critical id exception. Every sentence adds value, with no redundant filler or repetition of schema fields.

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?

Given seven parameters, no annotations, and no output schema, the description does a good job covering purpose, filtering behavior, record attributes, and the id override. It could be slightly more complete by explicitly stating the return shape (e.g., a list of events), but the mention of 'every record' and the response-count note in the schema compensate. Overall it is sufficiently complete for a read-oriented filter tool.

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?

The input schema already documents all seven parameters with 100% coverage, so the baseline is 3. The description adds minimal parameter-level meaning beyond what the schema provides; it repeats the id override behavior already in the schema and does not offer new syntax or formatting details for other parameters.

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 clearly states the tool finds upcoming Austin events from Yeehaw's sourced, deduplicated store, using a structured filter over the events table. It is specific about the resource and scope, distinguishing it from the only sibling 'overview' by positioning it as the queryable event store.

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?

The description provides clear context for when to use the tool and explains the special 'id' mode that ignores other filters. It does not explicitly mention when not to use it relative to the sibling 'overview' tool, but the filtering semantics and id behavior give sufficient practical guidance.

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

All events toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

find_events and overview have clearly distinct purposes: one queries events, the other reports system health. No overlap or ambiguity.

Naming Consistency4/5

Both use snake_case, but find_events follows a verb_noun pattern while overview is a standalone noun. Minor inconsistency but still readable.

Tool Count2/5

Only 2 tools for an events server feels underdeveloped. Typically such servers offer at least basic CRUD, making this count too low for the apparent scope.

Completeness2/5

Lacks essential operations like creating, updating, or deleting events. Only query and system health are present, leaving significant gaps.

Resources