Report a correction
dogpolicies_report_correctionReport an incorrect or outdated dog policy for a place, such as a fee change or beach closure, so a person can verify the official source before the record can change.
Instructions
Tell us a rule is wrong: the fee went up, a beach closed to dogs, a hotel now takes two pets. For a record the traveler says is wrong or out of date; this is the one tool that writes. The report goes to a person who re-reads the official source, and the record does not change until it is verified: a report is filed, not a fix. Inputs: place_id from a result, message (what is wrong, in the traveler's words), optional fact (which kind of fact is wrong), optional source_url of the official page, optional contact if the traveler offers one. No other personal detail is accepted. The answer carries a ticket id and a status_url. The ticket's status (filed, then verified or rejected) is public there; what they wrote is not.
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": {
"place_id": "<place_id>",
"message": "<message>"
},
"name": "dogpolicies_report_correction"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fact | No | What kind of rule is wrong, if clear. Shown on the public ticket; the message is not. | |
| contact | No | How to reach the reporter, only if they offer it | |
| message | Yes | What is wrong, in the user's words | |
| place_id | Yes | Place id from a search result | |
| source_url | No | The official page that shows the current rule, if the user has it |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| code | No | With an outcome other than ok: not_found, invalid, unavailable | |
| next | No | Calls that would answer the question, in words | |
| status | Yes | filed, or not_sent with form_url to file it by hand | |
| ticket | No | Public ticket id (c-xxxxxxxx) once filed; null otherwise | |
| 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 | |
| form_url | No | ||
| place_id | Yes | ||
| report_id | Yes | ||
| status_url | No | Where the ticket's status (filed, verified, rejected) is public | |
| 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 |