whats_on_tonight
One call for "what to do tonight in LA": top events until ~6am plus bars with happy hour on right now.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | ||
| lon | No |
event-synoptic
TDQS
B3.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description must carry the burden. It discloses time filters (events until ~6am, bars with happy hour now) but fails to mention output behavior, location dependence, or lack of results handling.
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 description is a single efficient sentence with no fluff, but its brevity sacrifices completeness, particularly regarding parameters.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 2 unannotated parameters and no output schema, the description lacks essential details about inputs, output format, and edge cases, making it insufficient for reliable agent invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description does not mention the lat/lon parameters at all, leaving their meaning and usage completely unspecified.
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 returns a combined list of top events and bars for tonight in LA, distinguishing it from sibling tools like find_bars or search_events.
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?
The description implies usage for tonight's combined events and bars, but does not explicitly state when to avoid this tool or mention alternatives beyond the implicit sibling distinction.
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.
TDQS
A4/5.0
Disambiguation5/5
Each tool has a clearly distinct role: venue finders (bars, museums), event search, ticket price comparison, event details, change history, taxonomy, and a curated nightly snapshot. While find_bars and search_events could theoretically overlap for nightlife, the descriptions explicitly scope them to venues vs. events, eliminating ambiguity.
Naming Consistency4/5
The tool names mostly follow a verb_noun pattern: find_* for venue discovery, get_* for retrieval, search_events for event search. However, `whats_on_tonight` breaks the pattern with an idiomatic phrase, and `find` vs `search` are used interchangeably for discovery, causing minor inconsistency.
Tool Count5/5
With 8 tools, the server is well-scoped for an LA event discovery service covering search, venue lookups, ticket prices, history, taxonomy, and a nightly roundup. Each tool earns its place without redundancy or bloat.
Completeness5/5
The tool surface covers the full read-only lifecycle: searching events, finding bars and museums, retrieving event details, comparing ticket prices, viewing historical changes, and exploring taxonomy tags. For its stated purpose of providing a synoptic LA event view, there are no significant gaps.