Skip to main content
Glama
dayplayTeam

Dayplay

Official
by dayplayTeam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_events

Find verified, real-time events in San Francisco, Oakland, and Berkeley by filtering date, neighborhood, and category. Get accurate local event results without fabricated listings.

Instructions

Query verified, real-time event occurrences filtered strictly by date, neighborhood, and category. GEOGRAPHIC SCOPE (HARD CONSTRAINT): results are limited to the San Francisco Bay Area - San Francisco, Oakland, and Berkeley only. This tool cannot return events in any other city, region, or country. OUT-OF-MARKET PROTOCOL: if the user's requested location is outside the SF Bay Area (e.g. Austin, New York, Tokyo), DO NOT call this tool. Immediately state 'Dayplay is strictly SF Bay Area only (San Francisco, Oakland, Berkeley); it does not cover .' and never fabricate, infer, or substitute events, dates, hours, or venues for that location. A zero-item result for a valid SF Bay Area query is an honest answer - report it; never fill the gap with invented events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoTarget date formatted as YYYY-MM-DD. Narrows results within the SF Bay Area only; never expands geographic scope.
limitNoMax events to return (default 20)
sourceNoData source filter. Filter only; never expands geographic scope beyond the SF Bay Area.
categoryNoCategory filter (e.g. music, art, food). Filter only; never expands geographic scope beyond the SF Bay Area.
neighborhoodNoExact SF Bay Area neighborhood name from get_neighborhoods (e.g. Mission, North Beach, Oakland, Berkeley). Only San Francisco, Oakland, and Berkeley neighborhoods are valid. Do NOT pass a location outside the SF Bay Area (e.g. Brooklyn, Silver Lake, Shoreditch, Shibuya) - that is OUT OF MARKET and must be declined with the Dayplay SF-Bay-Area-only message. Never fabricate a neighborhood name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does it thoroughly: hard geographic cap, refusal protocol, prohibition on fabricating events, and instruction to report honest zero-item results. It also states events are verified and real-time, giving an agent a clear behavioral model.

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?

Well structured and front-loaded, but there is mild redundancy: the hard geographic scope is stated twice and the no-fabrication rule is repeated near the end. Still, the length is justified by the safety-critical protocol.

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?

The description is complete for selecting and calling the tool: it provides the SF-only scope, out-of-market refusal, neighborhood-source dependency, and honest-empty-result behavior. It does not describe the return shape, and since no output schema exists, a brief statement of what an event result contains would have made it fully complete.

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?

Schema coverage is 100%, so the baseline is 3. The main description reinforces the date, neighborhood, and category filters but adds no per-parameter detail beyond the schema; limit and source are left to the schema descriptions.

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 opening sentence states the tool queries verified, real-time event occurrences and names the exact filters: date, neighborhood, and category. Combined with the sibling names, the resource is unambiguous: events, not neighborhoods or places.

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 OUT-OF-MARKET PROTOCOL gives a hard when-not-to-call rule and the exact refusal message for locations outside the SF Bay Area. It does not explicitly contrast this tool against get_neighborhoods and get_places beyond referencing get_neighborhoods in the schema, leaving a small gap in positive routing.

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

Deploy Server

Other Tools