Compare places side by side
dogpolicies_compare_placesCompare dog policies for two to six places side by side to check leash rules, pet fees, weight limits, and restrictions, with verified sources and freshness for each fact.
Instructions
Which of these places is better for my dog: Carmel Beach or Asilomar, two parks, three hotels? Sets two to six known places side by side, fact by fact. Input: ids from search results ("carmel-beach", "asilomar-state-beach"); an exact name or a near miss resolves to the one clear match. Returns one row per fact (dogs allowed, leash rule, where dogs may go, pet fee, weight limit, pets per room, restrictions) and one column per place, with confidence, freshness, who confirmed it, and a citation for each. An id that matches nothing is listed under missing with close matches while the rest are still compared (outcome partial); fewer than two found is no_match with suggestions.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"ids": "<ids>"
},
"name": "dogpolicies_compare_places"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ids | Yes | Two to six place ids from search results | |
| 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 | |
| rows | Yes | ||
| as_of | Yes | Date the data was built (YYYY-MM-DD) | |
| places | Yes | ||
| license | Yes | ||
| message | No | What happened, in a sentence | |
| missing | No | Ids nothing matched, each with its close matches | |
| 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 | |
| did_you_mean | No | Close matches to what was asked for: towns, places, slugs or brands, best first | |
| 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 |