Events for a date and location in San Francisco, Oakland, or Berkeley. Accepts neighborhood (e.g. 'Mission', 'SoMa') OR city-wide (e.g. 'San Francisco', 'Oakland', 'Berkeley').
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Calendar date, YYYY-MM-DD. | |
| limit | No | limit | |
| category | No | category | |
| neighborhood | No | San Francisco, Oakland, or Berkeley neighborhood name, such as Mission. |
Changes observed during successful MCP inspections.
Input schema / properties / sourceRemoved value: -{
- "description": "source",
- "type": "string"
-}Input schema / properties / category / descriptionAdded value: +"category"Input schema / properties / date / descriptionAdded value: +"Calendar date, YYYY-MM-DD."Input schema / properties / limit / descriptionAdded value: +"limit"Input schema / properties / limit / typePrevious value: -"string"New value: +"integer"Input schema / properties / neighborhood / descriptionAdded value: +"San Francisco, Oakland, or Berkeley neighborhood name, such as Mission."Input schema / properties / source / descriptionAdded value: +"source"Input schema / properties / category / descriptionRemoved value: -"Category filter (e.g. music, art, food). Filter only; never expands geographic scope beyond the SF Bay Area."Input schema / properties / date / descriptionRemoved value: -"Target date formatted as YYYY-MM-DD. Narrows results within the SF Bay Area only; never expands geographic scope."Input schema / properties / limit / descriptionRemoved value: -"Max events to return (default 20)"Input schema / properties / limit / typePrevious value: -"integer"New value: +"string"Input schema / properties / neighborhood / descriptionRemoved value: -"Exact 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."Input schema / properties / source / descriptionRemoved value: -"Data source filter. Filter only; never expands geographic scope beyond the SF Bay Area."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden, yet it discloses nothing about result volume, default limit behavior, sorting, pagination, or coverage (e.g., whether only today's events are returned). It only constrains the geographic scope, which is useful but thin for a read tool with zero structured hints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the resource and scope, and every clause carries information. The 'Accepts ... OR ...' phrasing is a little mechanical but not wasteful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 4-parameter tool with no annotations and no output schema, the description covers only date and location. The limit and category parameters are left entirely to the schema, and nothing explains what the response looks like or how many events to expect.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 description adds concrete example values for neighborhood ('Mission', 'SoMa') and the city-wide names, which slightly enriches the schema's own wording, but it says nothing about the limit or category parameters beyond what the schema already states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a clear verb+resource (events) plus the geographic and date scope, which is more than the bare name conveys. It does not, however, explicitly distinguish itself from close siblings like get_happening_today, get_weekend, or get_venue_events, so it falls short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains how to specify a location (neighborhood vs. city-wide) but never says when to choose this tool over alternatives such as get_happening_today, get_weekend, or get_venue_events. There is no exclusion guidance and no prerequisite information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.