Places in San Francisco, Oakland, or Berkeley. Accepts neighborhood (e.g. 'Mission', 'SoMa', 'San Francisco') and category (e.g. 'brunch', 'sports_bar', 'food', 'nightlife').
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | sort | |
| limit | No | limit | |
| category | No | category | |
| open_now | No | When true, only places open now. | |
| neighborhood | No | San Francisco, Oakland, or Berkeley neighborhood name, such as Mission. | |
| newly_opened_days | No | newly_opened_days |
Changes observed during successful MCP inspections.
Input schema / properties / categoryAdded value: +{
+ "description": "category",
+ "type": "string"
+}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 / newly_opened_days / descriptionAdded value: +"newly_opened_days"Input schema / properties / newly_opened_days / typePrevious value: -"string"New value: +"integer"Input schema / properties / open_now / descriptionAdded value: +"When true, only places open now."Input schema / properties / open_now / typePrevious value: -"string"New value: +"boolean"Input schema / properties / sort / descriptionAdded value: +"sort"Input schema / properties / limit / descriptionRemoved value: -"Max places 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. Williamsburg, Santa Monica, Camden, 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 / newly_opened_days / descriptionRemoved value: -"Filter for places opened in the last N days"Input schema / properties / newly_opened_days / typePrevious value: -"integer"New value: +"string"Input schema / properties / open_now / descriptionRemoved value: -"Filter strictly for SF Bay Area places open right now. Filter only; never expands geographic scope."Input schema / properties / open_now / typePrevious value: -"boolean"New value: +"string"Input schema / properties / sort / enumRemoved value: -[
- "rating",
- "distance"
-]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about read-only semantics, result volume, pagination, or default ordering. It only hints at filtering by neighborhood and category, which is a thin disclosure for a 6-parameter query tool.
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 tight sentences with no waste, and the geographic scope is front-loaded. It is efficient, though it spends its limited space on parameter examples rather than routing or behavioral context.
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 tool with 6 parameters, no annotations, no output schema, and no required parameters, the description omits critical context: how sorting and limiting behave, what newly_opened_days means, and how results are returned. It is not adequate for an agent to invoke the tool confidently.
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 description coverage is reported at 100%, so the baseline is 3, but several schema descriptions are bare placeholders ('sort', 'limit', 'category', 'newly_opened_days'). The description adds example values for category ('brunch', 'sports_bar', 'food', 'nightlife') that go somewhat beyond the schema, while its neighborhood examples largely duplicate the schema text.
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?
The description identifies the resource (places) and its geographic scope (San Francisco, Oakland, or Berkeley), but never states a clear verb or action, and does not distinguish this tool from near-identical siblings such as browse_places, get_marketing_places, or get_local_gems. An agent learns what kind of data is behind the tool but not why it should pick this one.
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?
There is no when-to-use guidance, no prerequisites, and no mention of alternatives. With over a dozen place/venue siblings available, the absence of routing advice leaves the agent to guess which tool to invoke.
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.