Follow rule changes in a feed
dogpolicies_subscribe_changesGet Atom and JSON feed links for dog rule changes by place, area, or highway stretch, plus 90-day change counts, to follow updates in any feed reader.
Instructions
Can you tell me if the dog rules change at Carmel Beach before our trip? Can I follow changes near Lake Tahoe, or along I-5? For hearing about changes later, without asking again: it answers with a feed link (Atom and JSON Feed) for one place, a town, county, area or neighborhood with a radius, or a highway's stops, which any feed reader can follow. It computes the links and counts only; it signs nobody up, stores nothing and sends no email. Inputs: one of place (a place id from any answer, e.g. "carmel-beach"), near (a town, county, area, region or neighborhood, e.g. "Lake Tahoe", "Monterey", "Van Nuys") with radius_miles, or route (i-5, us-101, highway-1, i-15, i-80, us-50, or a Nevada route ending in -nevada) with from_mile and to_mile. Returns atom_url and json_url, how many verification events, rule changes and corrections the scope had in the last 90 days, the page for the scope, and share_text: a sentence with the link, written for the traveler. An unknown name is an answer with did_you_mean.
Examples:
"Tell me if the rules change at Carmel Beach" -> place="carmel-beach"
"Can I get alerts for dog rule changes around Lake Tahoe?" -> near="Lake Tahoe"
"Follow changes on the Grapevine stretch of I-5" -> route="i-5", from_mile=170, to_mile=222
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "dogpolicies_subscribe_changes"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| near | No | A city, county, area, region or neighborhood in California or Nevada, e.g. "Lake Tahoe", "Monterey", "Washoe County, NV", "Van Nuys" | |
| place | No | One place by its id from any answer, e.g. "carmel-beach" (a close name is matched and labeled) | |
| route | No | A highway, e.g. "i-5", "us-101", "highway-1", "i-80-nevada" | |
| to_mile | No | With route: end of the stretch, in route miles | |
| from_mile | No | With route: start of the stretch, in route miles | |
| radius_miles | No | With near: miles around the town (an area or region is its own boundary; the radius is ignored) | |
| response_format | No | 'markdown' for readable text, 'json' for structured data | markdown |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | With an outcome other than ok: not_found, invalid, unavailable | |
| next | No | Calls that would answer the question, in words | |
| as_of | Yes | Date the data was built (YYYY-MM-DD) | |
| scope | Yes | What the feed follows: place, near or route, its id and label | |
| license | Yes | ||
| message | No | What happened, in a sentence | |
| nearest | No | When nothing is inside the radius: the nearest places in the data, with distance_miles | |
| outcome | No | Absent or ok: a normal answer. no_match: nothing in the data matches, see did_you_mean, nearest and next. bad_input: the arguments cannot be used as given, see next. partial: some of the ids were found, see missing. unavailable: a live source could not be read. None of these is an error. | |
| accepted | No | With bad_input: each argument that could not be read, with the values it accepts | |
| atom_url | Yes | The Atom 1.0 feed for the scope | |
| json_url | Yes | The JSON Feed 1.1 feed for the scope | |
| page_url | Yes | The page for the scope (the place's record or the road-trip guide), when there is one | |
| share_text | Yes | A sentence with the feed link, written for the traveler | |
| did_you_mean | No | Close matches to what was asked for: towns, places, slugs or brands, best first | |
| last_90_days | Yes | Activity in the scope over the last 90 days: verification events (re-checks included), rule changes (events whose outcome is changed, plus the rule-change log) and correction tickets (the hosted server only) | |
| resolved_from | No | Set when a word was read as the value the tool uses: hotel as lodging, NB as north. Each key is the argument; asked is what was sent, used what it was read as | |
| attribution_url | Yes | ||
| attribution_text | Yes |