dogpolicies-mcp 0.2.10 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -10,6 +10,103 @@ The data inside the package has its own date (`as_of` in every result). A
10
10
  new package version ships a new snapshot; the server also refreshes from the
11
11
  site on its own when the network allows.
12
12
 
13
+ ## 0.4.0 - 2026-11-07
14
+
15
+ Answers, not errors. A question the data cannot answer now comes back as a
16
+ normal answer that says so and helps, never as a dead end, and `isError` is
17
+ reserved for the server itself failing. Directories that score a server by
18
+ its `isError` rate (Claude's does) had been counting "Van Nuys is not a town
19
+ we cover" against us; what they count now is what a person would call an
20
+ error.
21
+
22
+ Changed
23
+
24
+ - `not_found`, `invalid`, `unavailable` and `offline` results are no longer
25
+ `isError`. They are answers with `outcome` (`no_match`, `bad_input`,
26
+ `partial` or `unavailable`), `code`, `message`, and whichever of
27
+ `did_you_mean` (close matches: towns, places, slugs, brands), `nearest` (the
28
+ nearest records anyway, with distance), `missing` and `next` (what to call)
29
+ apply. Every such answer still satisfies the tool's output schema: list
30
+ fields are empty, counts are zero, and a field with nothing honest to hold
31
+ is `null` (`near.center`, `get_rule.rule` and `.place`,
32
+ `i5_conditions.fetched_at`, `get_place.freshness` in a no-match answer).
33
+ A client that branched on `isError` for these codes should read `outcome`.
34
+ `isError` remains for `internal` and `rate_limited`.
35
+ - `dogpolicies_near` widens its radius on its own (30, 60, then 100 miles,
36
+ reported as `radius_widened_from`) when nothing sits inside the one asked
37
+ for, and when the data has nothing within 100 miles it lists the five
38
+ nearest records and the nearest towns with records.
39
+ - `dogpolicies_get_place` and `dogpolicies_compare_places` resolve a near
40
+ miss (a misspelled id, a name a word off) to the one clear match, labeled
41
+ `resolved_from`; `compare_places` compares what it found and lists the
42
+ rest under `missing` (`outcome: partial`).
43
+ - `dogpolicies_get_rule` with a rule id whose place exists but has no such
44
+ rule answers with that place and its recorded rule ids.
45
+ - `dogpolicies_browse_answers` with an unknown slug answers with the closest
46
+ slugs and the whole list; `dogpolicies_get_brand_policy` with an unknown
47
+ brand lists the covered brands nearest in spelling and how to check that
48
+ chain's hotels one by one.
49
+ - `dogpolicies_report_correction` with an unknown place answers
50
+ `bad_input` with close matches and files nothing; an unreachable inbox is
51
+ `unavailable` with the form's address.
52
+ - `dogpolicies_i5_conditions` reads the conditions document in-process on
53
+ the hosted server (it had been answering `offline` there since 0.3.0), marks
54
+ a reading older than two hours `stale`, and when no document can be read
55
+ answers `unavailable` with the live page's address. A point too far from
56
+ I-5 (also in `dogpolicies_i5_corridor`) answers `bad_input` with
57
+ `nearest_i5`: the nearest mile and how far it is.
58
+ - Numeric inputs accept numbers written as strings; `dogs` up to 10, `nights`
59
+ up to 90, `dog_weight_lb` up to 300, `max_total_fee` up to 10,000.
60
+ - The server instructions tell the model there are no dead ends and how to
61
+ use `outcome`, `did_you_mean`, `nearest` and `next`.
62
+
63
+ Fixed
64
+
65
+ - On I-5, `dogpolicies_route_stops`, `dogpolicies_i5_corridor` and the
66
+ drive leg of `dogpolicies_plan_trip` left out every park, hotel, campground
67
+ and patio on the far bank of the freeway: 195 of 422 stops northbound, 199
68
+ southbound (since 0.3.0). The geometric side of the road is now wording
69
+ only; a stop is one-way only when Caltrans lists it for one direction (a
70
+ rest area).
71
+ - The site's in-process server (`npm run preview`, stdio) now carries the
72
+ I-5 axis like the hosted Worker, so the three servers answer alike.
73
+
74
+ Added
75
+
76
+ - Output fields on every tool: `outcome`, `code`, `message`, `did_you_mean`,
77
+ `nearest`, `next` (all optional); `near.radius_widened_from` and `.nearest`;
78
+ `get_place.resolved_from`; `compare_places.missing`;
79
+ `i5_conditions.stale` and `.nearest_i5`; `i5_corridor.nearest_i5`;
80
+ `report_correction.form_url`.
81
+
82
+ ## 0.3.0 - 2026-11-04
83
+
84
+ The I-5 axis: every I-5 stop in California carries its position on the I-5
85
+ centerline (s meters from San Ysidro, the same number the corridor JSON and
86
+ the simulator use) beside its Caltrans mile.
87
+
88
+ Added
89
+
90
+ - `dogpolicies_route_stops`: `ahead_miles` (a window from the start in the
91
+ direction of travel), `family` (only stops whose official source states
92
+ restrooms and a pet area or dog park) and `paired` (exits with people-stops
93
+ nearby, counted from OpenStreetMap and never named, matched to the nearest
94
+ dog-legal place). On I-5 every stop returns `s_m`, `miles_ahead`, `side`,
95
+ `off_miles`, `elevation_m`, `strip`, `restrooms`, `water`, `pet_area`,
96
+ `dog_park`, `hours` (with its source) and `family_stop`.
97
+ - `dogpolicies_i5_corridor`: the eleven stretches of I-5 in California with
98
+ their s and mile ranges, and the stops in a stretch, a mile range or a
99
+ window ahead of a point.
100
+ - `dogpolicies_i5_conditions`: Caltrans lane closures, road-weather readings,
101
+ message-sign text and chain-control status on I-5, fetched within the last
102
+ 15 minutes and placed on the axis; conditions, not rules. Needs the network.
103
+ - `dogpolicies_get_place` returns `axis` and, for the dog side of a pairing,
104
+ `paired_stop`. `dogpolicies_plan_trip` returns `i5` (the drive leg's family
105
+ stops and paired stops) when the town is within 10 miles of I-5.
106
+ - Resource `dogpolicies://corridor/i-5`; prompt `drive_i5_with_dog`.
107
+ - The `hours` fact, in the source's own words.
108
+ - The snapshot carries the I-5 calibration table, strips and paired stops.
109
+
13
110
  ## 0.2.10 - 2026-11-04
14
111
 
15
112
  - Listed in Claude's connector directory: the README and the install guide
package/README.md CHANGED
@@ -23,7 +23,7 @@ npx dogpolicies-mcp demo
23
23
  - Whether dogs are allowed at 2,400+ parks, beaches, trails, hotels, campgrounds, cabin resorts and restaurant patios, with leash rules, restrictions, weight limits and pet fees.
24
24
  - Which hotel will take _your_ dog: weight, number of dogs, nights and a fee budget, with the fee arithmetic spelled out ("2 dogs x 3 nights x $25 per pet per night = $150, capped at $100 per stay").
25
25
  - A whole trip in one call: where to stay with this dog, what to do, where to eat, near any town or county.
26
- - Dog-friendly stops along I-5, US-101, Highway 1, I-15, I-80, US-50, US-95 and US-93, in driving order.
26
+ - Dog-friendly stops along I-5, US-101, Highway 1, I-15, I-80, US-50, US-95 and US-93, in driving order. On I-5 in California, every stop sits on the I-5 centerline (s meters from San Ysidro) with its side, elevation and stretch; the next family stop (restrooms and a pet area stated by the source) in N miles; paired exits; and Caltrans conditions right now.
27
27
  - Hotel chain pet policies (Motel 6, Red Roof, Kimpton and more) and which properties are exceptions.
28
28
  - Side-by-side comparisons, and what changed since a date, everywhere or near a town.
29
29
  - Areas the way travelers name them: East Bay, Lake Tahoe, Big Sur, Yosemite, Death Valley, the Mendocino Coast and the Bay Area's metros, as a filter, a place name in `near` and `plan_trip`, and a resource.
@@ -144,27 +144,29 @@ The `demo` output is the exact text an assistant receives:
144
144
 
145
145
  ## Tools
146
146
 
147
- | Tool | What it does |
148
- | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
149
- | `dogpolicies_search_places` | Search by name, type (beach, park, trail, lodging, campground, cabins, restaurant), county, state, region or a point and radius; filter to dogs allowed or off-leash. |
150
- | `dogpolicies_near` | Everything dog-related near a town, county or point, grouped by kind and sorted by distance. Takes a town name; no coordinates needed. |
151
- | `dogpolicies_get_place` | Full record for one place: every fact, its source with URL, date and quote, rule ids, and what the source does not state. |
152
- | `dogpolicies_compare_places` | Two to six places side by side: dogs allowed, leash, fee, weight limit, pets per room, freshness, who confirmed. |
153
- | `dogpolicies_plan_trip` | A stay in a town with this dog: stays that fit (fee for the whole stay worked out), beaches, parks, trails and patios nearby. |
154
- | `dogpolicies_find_hotels` | Hotels that take a specific dog: weight, number of dogs, nights, fee budget. Verdicts (match, possible, excluded), cheapest first, fee arithmetic shown. |
155
- | `dogpolicies_get_brand_policy` | A chain's published pet policy, its listed exceptions and property counts. |
156
- | `dogpolicies_browse_answers` | Ready-made answers to common questions ("Which California state parks allow dogs?"). |
157
- | `dogpolicies_route_stops` | Dog stops along a highway by mile and direction: rest areas with pet areas, hotels, campgrounds, parks, beaches. |
158
- | `dogpolicies_get_rule` | One rule by its stable id, with source, quote, confidence, verified date and freshness. |
159
- | `dogpolicies_changes_since` | Verification events and rule changes since a date, newest first. |
160
- | `dogpolicies_changes_near` | The same, limited to a radius around a town or point. |
161
- | `dogpolicies_report_correction` | Files a correction for a person to verify. Nothing is published automatically. The only tool that writes. |
162
-
163
- Every tool returns readable markdown by default and structured JSON (`response_format: "json"`), with an output schema. Every record carries `confidence` (stated, inferred_from_agency, inherited_brand), `freshness` (fresh, due, stale, unreadable, computed for today), `verified_at`, `url` and `source_urls`. Errors set `isError` with a code: `not_found`, `invalid`, `rate_limited`, `unavailable`, `offline`. The full reference, generated from the code, is [docs/tools.md](docs/tools.md).
147
+ | Tool | What it does |
148
+ | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
149
+ | `dogpolicies_search_places` | Search by name, type (beach, park, trail, lodging, campground, cabins, restaurant), county, state, region or a point and radius; filter to dogs allowed or off-leash. |
150
+ | `dogpolicies_near` | Everything dog-related near a town, county or point, grouped by kind and sorted by distance. Takes a town name; no coordinates needed. |
151
+ | `dogpolicies_get_place` | Full record for one place: every fact, its source with URL, date and quote, rule ids, and what the source does not state. |
152
+ | `dogpolicies_compare_places` | Two to six places side by side: dogs allowed, leash, fee, weight limit, pets per room, freshness, who confirmed. |
153
+ | `dogpolicies_plan_trip` | A stay in a town with this dog: stays that fit (fee for the whole stay worked out), beaches, parks, trails and patios nearby. |
154
+ | `dogpolicies_find_hotels` | Hotels that take a specific dog: weight, number of dogs, nights, fee budget. Verdicts (match, possible, excluded), cheapest first, fee arithmetic shown. |
155
+ | `dogpolicies_get_brand_policy` | A chain's published pet policy, its listed exceptions and property counts. |
156
+ | `dogpolicies_browse_answers` | Ready-made answers to common questions ("Which California state parks allow dogs?"). |
157
+ | `dogpolicies_route_stops` | Dog stops along a highway by mile and direction: rest areas with pet areas, hotels, campgrounds, parks, beaches. On I-5 in California: s meters from San Ysidro, side, elevation, family stops (restrooms and a pet area stated) and paired exits. |
158
+ | `dogpolicies_i5_corridor` | I-5 in California as eleven stretches on the I-5 centerline, and the stops in a stretch, a mile range or a window ahead of a point. |
159
+ | `dogpolicies_i5_conditions` | Caltrans closures, road weather, sign text and chain controls on I-5 right now, placed on the same axis; conditions, not rules. Needs the network. |
160
+ | `dogpolicies_get_rule` | One rule by its stable id, with source, quote, confidence, verified date and freshness. |
161
+ | `dogpolicies_changes_since` | Verification events and rule changes since a date, newest first. |
162
+ | `dogpolicies_changes_near` | The same, limited to a radius around a town or point. |
163
+ | `dogpolicies_report_correction` | Files a correction for a person to verify. Nothing is published automatically. The only tool that writes. |
164
+
165
+ Every tool returns readable markdown by default and structured JSON (`response_format: "json"`), with an output schema. Every record carries `confidence` (stated, inferred_from_agency, inherited_brand), `freshness` (fresh, due, stale, unreadable, computed for today), `verified_at`, `url` and `source_urls`. There are no dead ends: when nothing matches, the result is a normal answer with `outcome` (`no_match`, `bad_input`, `partial`, `unavailable`), `code`, `message`, and whichever of `did_you_mean` (close matches), `nearest` (the nearest records anyway), `missing` and `next` (what to call) apply. `isError` is set only when the server itself failed (`internal`) or refused a write (`rate_limited`). The full reference, generated from the code, is [docs/tools.md](docs/tools.md).
164
166
 
165
167
  ### Resources and prompts
166
168
 
167
- Resources let a client attach a record without a tool call: `dogpolicies://place/{id}`, `dogpolicies://brand/{id}`, `dogpolicies://answer/{slug}`, `dogpolicies://route/{id}`, `dogpolicies://area/{id}` (all with completion), plus `dogpolicies://about`, `dogpolicies://answers` and `dogpolicies://status`. Prompts give a client's slash menu the common trips: `plan_dog_trip`, `check_hotel_for_dog`, `road_trip_with_dog`, `what_can_my_dog_do_here`, `cite_a_rule`, with town-name completion.
169
+ Resources let a client attach a record without a tool call: `dogpolicies://place/{id}`, `dogpolicies://brand/{id}`, `dogpolicies://answer/{slug}`, `dogpolicies://route/{id}`, `dogpolicies://area/{id}` (all with completion), plus `dogpolicies://about`, `dogpolicies://answers`, `dogpolicies://status` and `dogpolicies://corridor/i-5` (the I-5 stretches and every stop by s). Prompts give a client's slash menu the common trips: `plan_dog_trip`, `check_hotel_for_dog`, `road_trip_with_dog`, `drive_i5_with_dog`, `what_can_my_dog_do_here`, `cite_a_rule`, with town-name completion.
168
170
 
169
171
  ## How the data stays current
170
172
 
Binary file
@@ -79,7 +79,10 @@ The core wraps each handler: the SDK validates input against the zod schema
79
79
  before the handler runs; a cached result is served when the data version and
80
80
  arguments match; a thrown `ToolError` becomes `{ isError, code }`; any other
81
81
  exception becomes `internal` with no stack in the result; the call is timed
82
- to the debug log. Resources (`{ uri | template, read }`) and prompts
82
+ to the debug log. A tool that finds nothing does not throw: it returns an
83
+ `answer()` (`core/errors.mjs`) whose `outcome` says what happened and whose
84
+ shape satisfies the tool's output schema, so the SDK's output validation
85
+ still runs on it and no directory counts it as an error. Resources (`{ uri | template, read }`) and prompts
83
86
  (`{ argsSchema, build }`) are registered the same way, with cache hints on
84
87
  the list methods and resource reads so 2026-07-28 clients can cache them.
85
88
 
package/docs/tools.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Tool reference
2
2
 
3
- dogpolicies-mcp 0.2.10, generated by `node scripts/docs.mjs` from the live definitions. Every tool returns readable markdown by default and structured JSON with `response_format: "json"`; every result starts with a citation and ends with the attribution line.
3
+ dogpolicies-mcp 0.4.0, generated by `node scripts/docs.mjs` from the live definitions. Every tool returns readable markdown by default and structured JSON with `response_format: "json"`; every result starts with a citation and ends with the attribution line.
4
4
 
5
5
  ## `dogpolicies_search_places`
6
6
 
@@ -8,7 +8,7 @@ dogpolicies-mcp 0.2.10, generated by `node scripts/docs.mjs` from the live defin
8
8
 
9
9
  Search parks, beaches, trails, hotels, campgrounds and cabin resorts in California and Nevada by name, location and dog rules.
10
10
 
11
- Returns one page of places with a one-line answer ("Yes, on a leash no longer than 6 feet."), status (yes, yes_restricted, no, varies), verification date and page URL. Each result includes the place id.
11
+ Returns one page of places with a one-line answer ("Yes, on a leash no longer than 6 feet."), status (yes, yes_restricted, no, varies), verification date and page URL. Each result includes the place id. When nothing matches, the answer (outcome no_match) carries close matches (did_you_mean: places and towns) and what to call next; a town name in query points to dogpolicies_near.
12
12
 
13
13
  Examples:
14
14
  - "Off-leash beaches near San Diego" -> type="beach", off_leash=true, near={lat:32.72, lon:-117.16}
@@ -37,7 +37,7 @@ Annotations: read-only true, destructive false, idempotent true, open-world fals
37
37
  | `offset` | integer (min 0, max 9007199254740991, default `0`) | Results to skip, for pagination |
38
38
  | `response_format` | `markdown`, `json` (default `"markdown"`) | 'markdown' for readable text, 'json' for structured data |
39
39
 
40
- Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `total`, `count`, `offset`, `has_more`, `places` (more may be added; none removed).
40
+ Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `outcome`, `code`, `message`, `did_you_mean`, `nearest`, `next`, `total`, `count`, `offset`, `has_more`, `places` (more may be added; none removed).
41
41
 
42
42
  ## `dogpolicies_near`
43
43
 
@@ -45,18 +45,19 @@ Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `total
45
45
 
46
46
  Anything for dogs around a town, county or point: everything dog-related nearby, grouped by kind: beaches, parks, trails, hotels, campgrounds, cabins, places to eat and rest areas, each sorted by distance, with the dog rule and citation for each. Answers "what can I do with my dog there?" for a named place.
47
47
 
48
- Takes a town or county name (no coordinates needed) or a point.
48
+ Takes a town, county, area, region or neighborhood name (no coordinates needed) or a point. Small spelling slips are corrected and labeled. When nothing is inside the radius, the search widens on its own (to 30, 60, then 100 miles) and says so; when the data has nothing near at all, the answer lists the nearest records anyway, so there is always something to offer. A name the data does not know comes back with close matches (did_you_mean) and what to call next, not an error.
49
49
 
50
50
  Examples:
51
51
  - "What can my dog do in Carmel?" -> place="Carmel"
52
52
  - "Dog beaches and parks around South Lake Tahoe" -> place="South Lake Tahoe", types=["beach","park"]
53
+ - "Anything dog-friendly in Van Nuys?" -> place="Van Nuys"
53
54
  - "Anything dog-friendly within 5 miles of here" -> near={lat:36.6, lon:-121.9}, radius_miles=5
54
55
 
55
56
  Annotations: read-only true, destructive false, idempotent true, open-world false.
56
57
 
57
58
  | Input | Type | Meaning |
58
59
  |---|---|---|
59
- | `place` | string (min length 2, max length 80) | A city, county or area in California or Nevada, e.g. "Monterey", "South Lake Tahoe", "Washoe County, NV", "Las Vegas", "East Bay" or "Lake Tahoe" |
60
+ | `place` | string (min length 2, max length 80) | A city, county, area, region or neighborhood in California or Nevada, e.g. "Monterey", "South Lake Tahoe", "Washoe County, NV", "Las Vegas", "East Bay", "Lake Tahoe", "Central Valley" or "Van Nuys". Small spelling slips are corrected and the answer says so. |
60
61
  | `near` | object | A point instead of a town; give one of place or near |
61
62
  | `radius_miles` | number (min 1, max 100, default `15`) | Search radius in miles around the town or point (an area is its own boundary; the radius is ignored) |
62
63
  | `types` | array of `beach`, `park`, `trail`, `lodging`, `campground`, `cabins`, `restaurant`, `rest_area`, `stop` | Kinds to include; all by default |
@@ -64,15 +65,15 @@ Annotations: read-only true, destructive false, idempotent true, open-world fals
64
65
  | `per_type` | integer (min 1, max 20, default `5`) | Nearest results to show per kind |
65
66
  | `response_format` | `markdown`, `json` (default `"markdown"`) | 'markdown' for readable text, 'json' for structured data |
66
67
 
67
- Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `center`, `label`, `radius_miles`, `total`, `groups` (more may be added; none removed).
68
+ Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `outcome`, `code`, `message`, `did_you_mean`, `nearest`, `next`, `center`, `label`, `radius_miles`, `radius_widened_from`, `total`, `groups` (more may be added; none removed).
68
69
 
69
70
  ## `dogpolicies_get_place`
70
71
 
71
72
  **Get place details** · since 0.1.0
72
73
 
73
- The full record for one place you already know by id: every dog rule with its display text, the rules list, and each source with its URL, publisher, capture date and quote.
74
+ The full record for one place you already know by id: every dog rule with its display text, the rules list, and each source with its URL, publisher, capture date and quote. A place on I-5 in California also carries its axis position (s meters from San Ysidro on the I-5 centerline, Caltrans mile, meters off the road, side of northbound travel, road elevation, strip) and, when it is the dog side of a paired stop, that pair: the exit and the people-stops near it (counted from OpenStreetMap, never named, not verified for restrooms).
74
75
 
75
- Takes a place id, as returned in every search result. Example: id="carmel-beach".
76
+ Takes a place id, as returned in every search result; a place's exact name works too, and a near miss resolves to the one clear match (labeled resolved_from). An id nothing matches comes back as an answer with close matches (did_you_mean), not an error. Example: id="carmel-beach".
76
77
 
77
78
  Annotations: read-only true, destructive false, idempotent true, open-world false.
78
79
 
@@ -81,7 +82,7 @@ Annotations: read-only true, destructive false, idempotent true, open-world fals
81
82
  | `id` (required) | string (min length 2, max length 120) | Place id, e.g. "fort-funston" |
82
83
  | `response_format` | `markdown`, `json` (default `"markdown"`) | 'markdown' for readable text, 'json' for structured data |
83
84
 
84
- Output fields: `id`, `uid`, `name`, `type`, `status`, `answer`, `citation`, `confidence`, `confirmed_by`, `freshness`, `verified_at`, `url`, `source_urls`, `record_license`, `as_of`, `license`, `attribution_text`, `attribution_url`, `facts`, `rule_records`, `not_stated`, `rules`, `sources`, `review_due` (more may be added; none removed).
85
+ Output fields: `id`, `uid`, `name`, `type`, `status`, `answer`, `citation`, `confidence`, `confirmed_by`, `freshness`, `verified_at`, `url`, `source_urls`, `record_license`, `as_of`, `license`, `attribution_text`, `attribution_url`, `outcome`, `code`, `message`, `did_you_mean`, `nearest`, `next`, `resolved_from`, `facts`, `rule_records`, `not_stated`, `rules`, `sources`, `review_due`, `axis`, `paired_stop` (more may be added; none removed).
85
86
 
86
87
  ## `dogpolicies_compare_places`
87
88
 
@@ -89,7 +90,7 @@ Output fields: `id`, `uid`, `name`, `type`, `status`, `answer`, `citation`, `con
89
90
 
90
91
  Which one is better for a dog? Compare two to six places on the facts that decide a dog trip: dogs allowed, leash rule, where dogs may go, pet fee, weight limit, pets per room, restrictions, plus confidence, freshness and who confirmed each record. One row per fact, one column per place, every place with its citation.
91
92
 
92
- Answers "which one?" between candidates; ids come from any search result. Example: ids=["carmel-beach","asilomar-state-beach"].
93
+ Answers "which one?" between candidates; ids come from any search result (an exact name or a near miss resolves to the one clear match). An id nothing matches is listed under missing with close matches, and the rest are still compared (outcome partial); with fewer than two found, the answer is no_match with suggestions. Example: ids=["carmel-beach","asilomar-state-beach"].
93
94
 
94
95
  Annotations: read-only true, destructive false, idempotent true, open-world false.
95
96
 
@@ -98,13 +99,13 @@ Annotations: read-only true, destructive false, idempotent true, open-world fals
98
99
  | `ids` (required) | array of string | Two to six place ids from search results |
99
100
  | `response_format` | `markdown`, `json` (default `"markdown"`) | 'markdown' for readable text, 'json' for structured data |
100
101
 
101
- Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `places`, `rows` (more may be added; none removed).
102
+ Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `outcome`, `code`, `message`, `did_you_mean`, `nearest`, `next`, `places`, `rows`, `missing` (more may be added; none removed).
102
103
 
103
104
  ## `dogpolicies_plan_trip`
104
105
 
105
106
  **Plan a trip with a dog** · since 0.2.0
106
107
 
107
- Plan a stay in a California or Nevada town with a dog, in one call: where to stay (hotels, campgrounds and cabins that will take this dog, with the pet fee for the whole stay worked out), what to do (beaches, parks and trails that allow dogs, nearest first) and where to eat (patios that take dogs), every item with its citation.
108
+ Plan a stay in a California or Nevada town with a dog, in one call: where to stay (hotels, campgrounds and cabins that will take this dog, with the pet fee for the whole stay worked out), what to do (beaches, parks and trails that allow dogs, nearest first) and where to eat (patios that take dogs), every item with its citation. When the town is within 10 miles of I-5 in California, the result also carries the drive leg on the I-5 axis: the town's position (Caltrans mile and s meters from San Ysidro), the next family stops (restrooms and a pet area or dog park stated by their official source) in each direction within 60 miles, and the paired stops (an exit with people-stops nearby, counted from OpenStreetMap and never named, matched to the nearest dog-legal place) within 10 miles.
108
109
 
109
110
  Inputs: the town or county and the dog: weight, how many dogs, nights, and the most the user will pay in pet fees.
110
111
 
@@ -117,19 +118,19 @@ Annotations: read-only true, destructive false, idempotent true, open-world fals
117
118
 
118
119
  | Input | Type | Meaning |
119
120
  |---|---|---|
120
- | `place` | string (min length 2, max length 80) | A city, county or area in California or Nevada, e.g. "Monterey", "South Lake Tahoe", "Washoe County, NV", "Las Vegas", "East Bay" or "Lake Tahoe" |
121
+ | `place` | string (min length 2, max length 80) | A city, county, area, region or neighborhood in California or Nevada, e.g. "Monterey", "South Lake Tahoe", "Washoe County, NV", "Las Vegas", "East Bay", "Lake Tahoe", "Central Valley" or "Van Nuys". Small spelling slips are corrected and the answer says so. |
121
122
  | `near` | object | A point instead of a town; give one of place or near |
122
123
  | `radius_miles` | number (min 1, max 100, default `15`) | Search radius in miles around the town or point (an area is its own boundary; the radius is ignored) |
123
- | `dog_weight_lb` | number (min 1, max 250) | The dog's weight in pounds |
124
- | `dogs` | integer (min 1, max 4, default `1`) | Number of dogs |
125
- | `nights` | integer (min 1, max 30, default `1`) | Nights of the stay |
126
- | `max_total_fee` | number (min 0, max 5000) | Most the guest will pay in pet fees for the whole stay, USD |
124
+ | `dog_weight_lb` | number (min 1, max 300) | The dog's weight in pounds |
125
+ | `dogs` | integer (min 1, max 10, default `1`) | Number of dogs |
126
+ | `nights` | integer (min 1, max 90, default `1`) | Nights of the stay |
127
+ | `max_total_fee` | number (min 0, max 10000) | Most the guest will pay in pet fees for the whole stay, USD |
127
128
  | `stay_types` | array of `lodging`, `campground`, `cabins` (default `["lodging","campground","cabins"]`) | Kinds of stay to consider |
128
129
  | `include_possible` | boolean (default `true`) | Include stays that need a call to confirm |
129
130
  | `per_section` | integer (min 1, max 15, default `5`) | Results per section |
130
131
  | `response_format` | `markdown`, `json` (default `"markdown"`) | 'markdown' for readable text, 'json' for structured data |
131
132
 
132
- Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `label`, `radius_miles`, `asked`, `stays`, `stay_counts`, `outings` (more may be added; none removed).
133
+ Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `outcome`, `code`, `message`, `did_you_mean`, `nearest`, `next`, `label`, `radius_miles`, `asked`, `stays`, `stay_counts`, `outings`, `i5` (more may be added; none removed).
133
134
 
134
135
  ## `dogpolicies_find_hotels`
135
136
 
@@ -153,10 +154,10 @@ Annotations: read-only true, destructive false, idempotent true, open-world fals
153
154
  |---|---|---|
154
155
  | `query` | string (min length 2, max length 100) | Words in the hotel name, city or brand |
155
156
  | `brand` | `best-western`, `extended-stay-america`, `kimpton`, `la-quinta`, `motel-6`, `red-roof` | Only this hotel brand |
156
- | `dog_weight_lb` | number (min 1, max 250) | The dog's weight in pounds |
157
- | `dogs` | integer (min 1, max 4, default `1`) | Number of dogs |
158
- | `nights` | integer (min 1, max 30, default `1`) | Nights of the stay |
159
- | `max_total_fee` | number (min 0, max 5000) | Most the guest will pay in pet fees for the whole stay, USD |
157
+ | `dog_weight_lb` | number (min 1, max 300) | The dog's weight in pounds |
158
+ | `dogs` | integer (min 1, max 10, default `1`) | Number of dogs |
159
+ | `nights` | integer (min 1, max 90, default `1`) | Nights of the stay |
160
+ | `max_total_fee` | number (min 0, max 10000) | Most the guest will pay in pet fees for the whole stay, USD |
160
161
  | `include_possible` | boolean (default `true`) | Include hotels that need a call to confirm |
161
162
  | `state` | `CA`, `NV` | "CA" or "NV". Also tells apart counties with the same name, such as Humboldt. |
162
163
  | `county` | string (min length 2, max length 40) | County name without "County", in California or Nevada, e.g. "Monterey" or "Washoe" |
@@ -167,7 +168,7 @@ Annotations: read-only true, destructive false, idempotent true, open-world fals
167
168
  | `offset` | integer (min 0, max 9007199254740991, default `0`) | Results to skip, for pagination |
168
169
  | `response_format` | `markdown`, `json` (default `"markdown"`) | 'markdown' for readable text, 'json' for structured data |
169
170
 
170
- Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `total`, `count`, `offset`, `has_more`, `hotels`, `counts` (more may be added; none removed).
171
+ Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `outcome`, `code`, `message`, `did_you_mean`, `nearest`, `next`, `total`, `count`, `offset`, `has_more`, `hotels`, `counts` (more may be added; none removed).
171
172
 
172
173
  ## `dogpolicies_get_brand_policy`
173
174
 
@@ -184,7 +185,7 @@ Annotations: read-only true, destructive false, idempotent true, open-world fals
184
185
  | `brand` (required) | string (min length 2, max length 60) | Brand id or name |
185
186
  | `response_format` | `markdown`, `json` (default `"markdown"`) | 'markdown' for readable text, 'json' for structured data |
186
187
 
187
- Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `id`, `name`, `answer`, `facts`, `not_stated`, `verified_at`, `url`, `source_urls` (more may be added; none removed).
188
+ Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `outcome`, `code`, `message`, `did_you_mean`, `nearest`, `next`, `resolved_from`, `id`, `name`, `answer`, `facts`, `not_stated`, `verified_at`, `url`, `source_urls` (more may be added; none removed).
188
189
 
189
190
  ## `dogpolicies_browse_answers`
190
191
 
@@ -203,7 +204,7 @@ Annotations: read-only true, destructive false, idempotent true, open-world fals
203
204
  | `offset` | integer (min 0, max 9007199254740991, default `0`) | Results to skip, for pagination |
204
205
  | `response_format` | `markdown`, `json` (default `"markdown"`) | 'markdown' for readable text, 'json' for structured data |
205
206
 
206
- Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `total`, `questions`, `places` (more may be added; none removed).
207
+ Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `outcome`, `code`, `message`, `did_you_mean`, `nearest`, `next`, `total`, `questions`, `places` (more may be added; none removed).
207
208
 
208
209
  ## `dogpolicies_route_stops`
209
210
 
@@ -211,13 +212,17 @@ Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `total
211
212
 
212
213
  Dog-friendly stops along a California or Nevada highway, in driving order: rest areas (Caltrans rest areas with pet areas; Nevada rest areas, where leashed dogs are allowed), travel stops with dog parks, hotels, cabin resorts and campgrounds or RV parks near the road (all checked against the dog's weight and the pet-fee budget) and parks or beaches that allow dogs.
213
214
 
214
- Each stop has its mile on the route and its distance off the road. Each route covers one state and stops at the state line. California miles follow the Caltrans odometer: north on I-5 (from the Mexican border), US-101 (from Los Angeles), Highway 1 (from Dana Point) and I-15 (i-15, San Diego to Primm); east on I-80 (i-80, San Francisco to the Nevada line) and US-50 (us-50, West Sacramento to Stateline). Nevada routes count Nevada mileposts from the California line, matching the exit numbers: north on I-15 (i-15-nevada), east on I-80 (i-80-nevada) and US-50 (us-50-nevada, Stateline to Utah); north on US-95 (us-95-nevada, California line to Oregon) and US-93 (us-93-nevada, Hoover Dam to Idaho), whose miles include the stretches they share with other highways. Where Highway 1 runs on US-101, stops on that stretch say so in on_road. A starting point is set with from_mile or near, plus a direction.
215
+ Each stop has its mile on the route and its distance off the road. Each route covers one state and stops at the state line. California miles follow the Caltrans odometer: north on I-5 (from the Mexican border), US-101 (from Los Angeles), Highway 1 (from Dana Point) and I-15 (i-15, San Diego to Primm); east on I-80 (i-80, San Francisco to the Nevada line) and US-50 (us-50, West Sacramento to Stateline). Nevada routes count Nevada mileposts from the California line, matching the exit numbers: north on I-15 (i-15-nevada), east on I-80 (i-80-nevada) and US-50 (us-50-nevada, Stateline to Utah); north on US-95 (us-95-nevada, California line to Oregon) and US-93 (us-93-nevada, Hoover Dam to Idaho), whose miles include the stretches they share with other highways. Where Highway 1 runs on US-101, stops on that stretch say so in on_road. A starting point is set with from_mile or near, plus a direction; ahead_miles limits the window to that many miles from the start in the direction of travel.
216
+
217
+ On I-5 in California each stop also carries its position on the I-5 centerline in meters from San Ysidro (s_m), miles_ahead of the start along the direction of travel, the side of the road it serves (right or left of northbound travel, or both), its distance off the freeway, the road's elevation in meters and the stretch (strip) it is in, plus restrooms, water, pet_area, dog_park and hours as its official source states them. With family=true only stops whose official source states restrooms and a pet area or dog park are returned. With paired=true the result also lists paired stops: a freeway exit in the window with places to stop for people nearby (located through OpenStreetMap, counted by kind, never named and not verified for restrooms) matched to the nearest DogPolicies place that allows dogs within about a mile, with its rule and source.
215
218
 
216
219
  Routes covered: I-5 (i-5, 796 miles), US-101 (us-101, 809 miles), Highway 1 (highway-1, 736 miles), I-15 (i-15, 294 miles), I-80 (i-80, 204 miles), US-50 (us-50, 109 miles), I-15 (i-15-nevada, 124 miles), I-80 (i-80-nevada, 410 miles), US-50 (us-50-nevada, 409 miles), US-95 (us-95-nevada, 664 miles), US-93 (us-93-nevada, 526 miles).
217
220
 
218
221
  Examples:
219
222
  - "Driving north on I-5 from Los Angeles with a 70 lb dog, where can we stop?" -> near={lat:34.05, lon:-118.24}, direction="north", dog_weight_lb=70
220
223
  - "Pet areas on the Grapevine" -> from_mile=170, to_mile=222, kinds=["rest_area","park"]
224
+ - "Next place in 40 miles where the whole family can use a restroom, dog included, northbound at Harris Ranch" -> near={lat:36.25, lon:-120.25}, direction="north", ahead_miles=40, family=true
225
+ - "Exits with a coffee shop and a park for the dog between Sacramento and Redding" -> from_mile=520, to_mile=680, paired=true
221
226
  - "Heading south on 101 from San Francisco to Santa Barbara, where can the dog run?" -> route="us-101", near={lat:37.77, lon:-122.42}, to_mile=100, direction="south"
222
227
  - "Dog-friendly hotel near Redding under $40 a night" -> near={lat:40.59, lon:-122.39}, kinds=["lodging"], max_total_fee=40
223
228
  - "Driving I-80 east from Reno with a dog, where can we stop?" -> route="i-80-nevada", near={lat:39.53, lon:-119.81}, direction="east"
@@ -230,18 +235,80 @@ Annotations: read-only true, destructive false, idempotent true, open-world fals
230
235
  | `near` | object | Start from the route mile nearest this point |
231
236
  | `from_mile` | number (min 0, max 1000) | Start at this route mile |
232
237
  | `to_mile` | number (min 0, max 1000) | Stop at this route mile |
238
+ | `ahead_miles` | number (min 1, max 1000) | Window in miles from the start (near or from_mile) in the direction of travel; an alternative to to_mile |
233
239
  | `direction` | `north`, `south`, `east`, `west` (default `"north"`) | Direction of travel. Route miles increase going north, or east on I-80 and US-50; north and east both mean increasing miles |
234
240
  | `kinds` | array of `rest_area`, `stop`, `lodging`, `campground`, `cabins`, `park`, `beach`, `trail`, `restaurant` | Kinds of stops to include; all by default |
241
+ | `family` | boolean (default `false`) | Only stops whose official source states restrooms and a pet area or dog park (I-5 in California) |
242
+ | `paired` | boolean (default `false`) | Also list the paired stops in the window: an exit with people-stops nearby and the nearest dog-legal place (I-5 in California) |
235
243
  | `dog_friendly_only` | boolean (default `true`) | Leave out stops where dogs are not allowed |
236
- | `dog_weight_lb` | number (min 1, max 250) | The dog's weight in pounds |
237
- | `dogs` | integer (min 1, max 4, default `1`) | Number of dogs |
238
- | `nights` | integer (min 1, max 30, default `1`) | Nights of the stay |
239
- | `max_total_fee` | number (min 0, max 5000) | Most the guest will pay in pet fees for the whole stay, USD |
244
+ | `dog_weight_lb` | number (min 1, max 300) | The dog's weight in pounds |
245
+ | `dogs` | integer (min 1, max 10, default `1`) | Number of dogs |
246
+ | `nights` | integer (min 1, max 90, default `1`) | Nights of the stay |
247
+ | `max_total_fee` | number (min 0, max 10000) | Most the guest will pay in pet fees for the whole stay, USD |
240
248
  | `limit` | integer (min 1, max 50, default `10`) | Maximum results to return |
241
249
  | `offset` | integer (min 0, max 9007199254740991, default `0`) | Results to skip, for pagination |
242
250
  | `response_format` | `markdown`, `json` (default `"markdown"`) | 'markdown' for readable text, 'json' for structured data |
243
251
 
244
- Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `total`, `count`, `offset`, `has_more`, `stops`, `route`, `guide` (more may be added; none removed).
252
+ Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `outcome`, `code`, `message`, `did_you_mean`, `nearest`, `next`, `total`, `count`, `offset`, `has_more`, `stops`, `route`, `guide`, `start`, `paired_stops` (more may be added; none removed).
253
+
254
+ ## `dogpolicies_i5_corridor`
255
+
256
+ **I-5 corridor by stretch** · since 0.3.0
257
+
258
+ The I-5 corridor in California as eleven named stretches (strips) on the I-5 centerline, from San Ysidro (s = 0 m) to the Oregon line (s ≈ 1,281,400 m), and the dog stops in any stretch, mile range or window ahead of a point. Every stop carries its s in meters from San Ysidro, its Caltrans odometer mile, the side of the road it serves (right or left of northbound travel, or both), its distance off the freeway, the road's elevation, and restrooms, water, pet area, dog park and hours as its official source states them. A family stop is one whose official source states restrooms and a pet area or dog park. A paired stop is a freeway exit with places to stop for people nearby (located through OpenStreetMap, counted by kind, never named and not verified for restrooms) matched to the nearest DogPolicies place that allows dogs within about a mile, with its rule and source.
259
+
260
+ With no stretch, miles or point, the result is the list of stretches with their s and mile ranges and stop counts. Strips: sandiego (San Ysidro → Camp Pendleton), orange-la (Camp Pendleton → East LA), grapevine (East LA → Wheeler Ridge), kern-westside (Wheeler Ridge → Kettleman), westside (Kettleman → Santa Nella), delta (Santa Nella → Stockton), sacramento (Stockton → Woodland), valley (Woodland → Williams), tehama (Williams → Red Bluff), shasta (Red Bluff → Mt Shasta), siskiyou (Mt Shasta → Siskiyou Summit).
261
+
262
+ Examples:
263
+ - "What is between the Grapevine and Kettleman?" -> strip="grapevine" (East LA to Wheeler Ridge) and strip="kern-westside" (Wheeler Ridge to Kettleman)
264
+ - "The next 5 family stops northbound from Stockton" -> near={lat:37.95, lon:-121.29}, direction="north", family=true, limit=5
265
+ - "Every stop between mile 300 and 340" -> from_mile=300, to_mile=340
266
+ - "Exits with somewhere for people and a park for the dog in the Sacramento stretch" -> strip="sacramento", paired=true
267
+
268
+ Annotations: read-only true, destructive false, idempotent true, open-world false.
269
+
270
+ | Input | Type | Meaning |
271
+ |---|---|---|
272
+ | `strip` | `sandiego`, `orange-la`, `grapevine`, `kern-westside`, `westside`, `delta`, `sacramento`, `valley`, `tehama`, `shasta`, `siskiyou` | A stretch by id (sandiego, orange-la, grapevine, kern-westside, westside, delta, sacramento, valley, tehama, shasta, siskiyou) |
273
+ | `from_mile` | number (min 0, max 800) | Start of a mile range (Caltrans odometer) |
274
+ | `to_mile` | number (min 0, max 800) | End of a mile range |
275
+ | `near` | object | A point on or near I-5; the window starts at the nearest point of the road |
276
+ | `direction` | `north`, `south` (default `"north"`) | Direction of travel from near; north means increasing s |
277
+ | `ahead_miles` | number (min 1, max 800, default `50`) | Window in miles from near in the direction of travel |
278
+ | `kinds` | array of `rest_area`, `stop`, `lodging`, `campground`, `cabins`, `park`, `beach`, `trail`, `restaurant` | Kinds of stops to include; all by default |
279
+ | `family` | boolean (default `false`) | Only family stops |
280
+ | `paired` | boolean (default `false`) | Also list the paired stops in the window |
281
+ | `dog_friendly_only` | boolean (default `true`) | Leave out stops where dogs are not allowed |
282
+ | `limit` | integer (min 1, max 50, default `15`) | Maximum stops to return |
283
+ | `offset` | integer (min 0, max 9007199254740991, default `0`) | Stops to skip |
284
+ | `response_format` | `markdown`, `json` (default `"markdown"`) | 'markdown' for readable text, 'json' for structured data |
285
+
286
+ Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `outcome`, `code`, `message`, `did_you_mean`, `nearest`, `next`, `nearest_i5`, `axis_version`, `strips`, `window`, `total`, `stops`, `paired_stops` (more may be added; none removed).
287
+
288
+ ## `dogpolicies_i5_conditions`
289
+
290
+ **I-5 conditions now** · since 0.3.0
291
+
292
+ Current Caltrans lane closures, road-weather station readings, changeable-message-sign text and chain-control status on I-5 in California, each placed on the I-5 centerline (s meters from San Ysidro and the Caltrans mile) and matched to the nearest DogPolicies dog stop. Conditions come from Caltrans' CWWP2 feeds fetched within the last 15 minutes (fetched_at in the result) and are not verified rules.
293
+
294
+ The window is a mile range (from_mile, to_mile) or a point with a direction and ahead_miles; with none, the whole of I-5 in California. When the document cannot be read (no network, feeds down), the answer has outcome unavailable and the live page's address; a document older than two hours is marked stale.
295
+
296
+ Examples:
297
+ - "Is there a closure or chains on the Grapevine right now?" -> from_mile=170, to_mile=222
298
+ - "Weather and closures in the next 60 miles northbound from Redding" -> near={lat:40.59, lon:-122.39}, direction="north", ahead_miles=60
299
+
300
+ Annotations: read-only true, destructive false, idempotent true, open-world false.
301
+
302
+ | Input | Type | Meaning |
303
+ |---|---|---|
304
+ | `from_mile` | number (min 0, max 800) | Start of a mile range |
305
+ | `to_mile` | number (min 0, max 800) | End of a mile range |
306
+ | `near` | object | A point on or near I-5 |
307
+ | `direction` | `north`, `south` (default `"north"`) | Direction of travel from near |
308
+ | `ahead_miles` | number (min 1, max 800, default `50`) | Window in miles from near |
309
+ | `response_format` | `markdown`, `json` (default `"markdown"`) | 'markdown' for readable text, 'json' for structured data |
310
+
311
+ Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `outcome`, `code`, `message`, `did_you_mean`, `nearest`, `next`, `fetched_at`, `stale`, `notice`, `window`, `chains_in_effect`, `closures`, `weather`, `signs`, `chain_controls`, `source`, `nearest_i5` (more may be added; none removed).
245
312
 
246
313
  ## `dogpolicies_get_rule`
247
314
 
@@ -256,7 +323,7 @@ Annotations: read-only true, destructive false, idempotent true, open-world fals
256
323
  | `id` (required) | string (min length 6, max length 80) | Rule id, e.g. "rul_t6cqwy0x4ce2dmpq_fee" |
257
324
  | `response_format` | `markdown`, `json` (default `"markdown"`) | 'markdown' for readable text, 'json' for structured data |
258
325
 
259
- Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `rule`, `place` (more may be added; none removed).
326
+ Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `outcome`, `code`, `message`, `did_you_mean`, `nearest`, `next`, `rule`, `place` (more may be added; none removed).
260
327
 
261
328
  ## `dogpolicies_changes_since`
262
329
 
@@ -288,7 +355,7 @@ Annotations: read-only true, destructive false, idempotent true, open-world fals
288
355
 
289
356
  | Input | Type | Meaning |
290
357
  |---|---|---|
291
- | `place` | string (min length 2, max length 80) | A city, county or area in California or Nevada, e.g. "Monterey", "South Lake Tahoe", "Washoe County, NV", "Las Vegas", "East Bay" or "Lake Tahoe" |
358
+ | `place` | string (min length 2, max length 80) | A city, county, area, region or neighborhood in California or Nevada, e.g. "Monterey", "South Lake Tahoe", "Washoe County, NV", "Las Vegas", "East Bay", "Lake Tahoe", "Central Valley" or "Van Nuys". Small spelling slips are corrected and the answer says so. |
292
359
  | `near` | object | A point instead of a town; give one of place or near |
293
360
  | `radius_miles` | number (min 1, max 100, default `15`) | Search radius in miles around the town or point (an area is its own boundary; the radius is ignored) |
294
361
  | `since` (required) | string | Date, YYYY-MM-DD |
@@ -297,7 +364,7 @@ Annotations: read-only true, destructive false, idempotent true, open-world fals
297
364
  | `offset` | integer (min 0, max 9007199254740991, default `0`) | Results to skip, for pagination |
298
365
  | `response_format` | `markdown`, `json` (default `"markdown"`) | 'markdown' for readable text, 'json' for structured data |
299
366
 
300
- Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `label`, `radius_miles`, `total`, `count`, `has_more`, `events` (more may be added; none removed).
367
+ Output fields: `as_of`, `license`, `attribution_text`, `attribution_url`, `outcome`, `code`, `message`, `did_you_mean`, `nearest`, `next`, `label`, `radius_miles`, `total`, `count`, `has_more`, `events` (more may be added; none removed).
301
368
 
302
369
  ## `dogpolicies_report_correction`
303
370
 
@@ -314,7 +381,7 @@ Annotations: read-only false, destructive false, idempotent false, open-world tr
314
381
  | `source_url` | string (max length 500) | The official page that shows the current rule, if the user has it |
315
382
  | `contact` | string (max length 200) | How to reach the reporter, only if they offer it |
316
383
 
317
- Output fields: `report_id`, `place_id`, `status`, `url` (more may be added; none removed).
384
+ Output fields: `outcome`, `code`, `message`, `did_you_mean`, `nearest`, `next`, `report_id`, `place_id`, `status`, `url`, `form_url` (more may be added; none removed).
318
385
 
319
386
  # Resources
320
387
 
@@ -327,6 +394,7 @@ Output fields: `report_id`, `place_id`, `status`, `url` (more may be added; none
327
394
  | `dogpolicies://brand/{id}` | A chain's published pet policy, exceptions and property counts | text/markdown |
328
395
  | `dogpolicies://answer/{slug}` | The places that answer one ready-made question | text/markdown |
329
396
  | `dogpolicies://route/{id}` | Dog-friendly stops along one highway in driving order | text/markdown |
397
+ | `dogpolicies://corridor/i-5` | I-5 in California as eleven stretches on the I-5 centerline (s meters from San Ysidro), with every dog stop at its s, the family stops and the paired stops | application/json |
330
398
  | `dogpolicies://area/{id}` | Every dog-related place in one area (East Bay, Lake Tahoe, Big Sur), grouped by kind | text/markdown |
331
399
 
332
400
  Templates support completion (`completion/complete`) for their variable.
@@ -338,5 +406,6 @@ Templates support completion (`completion/complete`) for their variable.
338
406
  | `plan_dog_trip` | A stay in a California or Nevada town: where to stay with this dog, what to do, where to eat, with sources | `destination`, `dog`, `nights`, `budget` |
339
407
  | `check_hotel_for_dog` | Check one hotel or a town's hotels against a specific dog: weight, count, nights, fee | `hotel_or_town`, `dog_weight_lb`, `dogs`, `nights` |
340
408
  | `road_trip_with_dog` | Dog-friendly stops along a highway in driving order: rest areas, parks, hotels within budget | `route`, `from`, `direction`, `dog_weight_lb` |
409
+ | `drive_i5_with_dog` | The drive on I-5 in California: the next family stops (restrooms and a pet area) and paired exits ahead, with conditions now | `from`, `direction`, `ahead_miles` |
341
410
  | `what_can_my_dog_do_here` | Beaches, parks, trails, patios and stays near a town, with the rule for each | `place` |
342
411
  | `cite_a_rule` | The official rule for one place with the quoted source text, ready to cite | `place_id` |
@@ -21,8 +21,10 @@ treated elsewhere, so nothing breaks in a 0.x minor either).
21
21
  - Output fields named in each tool's `outputSchema`, and the shape of the
22
22
  envelope (`as_of`, `license`, `attribution_text`, `attribution_url`,
23
23
  `total`, `count`, `offset`, `has_more`, `next_offset`).
24
- - Error codes: `not_found`, `invalid`, `rate_limited`, `unavailable`,
25
- `offline`, `internal`.
24
+ - Outcomes and codes: an answer's `outcome` (`ok`, `partial`, `no_match`,
25
+ `bad_input`, `unavailable`) and `code` (`not_found`, `invalid`,
26
+ `unavailable`); the error codes `internal` and `rate_limited`, the only
27
+ ones that set `isError` (since 0.4.0).
26
28
  - Resource URIs and prompt names.
27
29
  - The first line of every markdown result being a citation and the last the
28
30
  attribution line.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "dogpolicies-mcp",
3
- "version": "0.2.10",
3
+ "version": "0.4.0",
4
4
  "description": "MCP server for verified dog rules at California and Nevada parks, beaches, trails, hotels, campgrounds and restaurant patios: leash rules, pet fees, weight limits, trip planning, every fact with its official source and the date it was checked.",
5
5
  "mcpName": "io.github.xultrax-web/dogpolicies-mcp",
6
6
  "type": "module",
package/server.json CHANGED
@@ -8,13 +8,13 @@
8
8
  "url": "https://github.com/xultrax-web/dogpolicies-mcp",
9
9
  "source": "github"
10
10
  },
11
- "version": "0.2.10",
11
+ "version": "0.4.0",
12
12
  "packages": [
13
13
  {
14
14
  "registryType": "npm",
15
15
  "registryBaseUrl": "https://registry.npmjs.org",
16
16
  "identifier": "dogpolicies-mcp",
17
- "version": "0.2.10",
17
+ "version": "0.4.0",
18
18
  "runtimeHint": "npx",
19
19
  "transport": {
20
20
  "type": "stdio"
@@ -48,7 +48,7 @@
48
48
  "tool": "dogpolicies-release",
49
49
  "license": "code MIT; data CC BY 4.0 (chain-hotel names and locations ODbL)",
50
50
  "coverage": "California and Nevada",
51
- "tools": 13
51
+ "tools": 15
52
52
  }
53
53
  }
54
54
  }