Skip to main content
Glama
DogPolicies MCP Server

DogPolicies MCP Server

by xultrax-web

Report a correction

dogpolicies_report_correction

Report 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

NameRequiredDescriptionDefault
factNoWhat kind of rule is wrong, if clear. Shown on the public ticket; the message is not.
contactNoHow to reach the reporter, only if they offer it
messageYesWhat is wrong, in the user's words
place_idYesPlace id from a search result
source_urlNoThe official page that shows the current rule, if the user has it

Output Schema

NameRequiredDescriptionDefault
urlYes
codeNoWith an outcome other than ok: not_found, invalid, unavailable
nextNoCalls that would answer the question, in words
statusYesfiled, or not_sent with form_url to file it by hand
ticketNoPublic ticket id (c-xxxxxxxx) once filed; null otherwise
messageNoWhat happened, in a sentence
nearestNoWhen nothing is inside the radius: the nearest places in the data, with distance_miles
outcomeNoAbsent 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.
acceptedNoWith bad_input: each argument that could not be read, with the values it accepts
form_urlNo
place_idYes
report_idYes
status_urlNoWhere the ticket's status (filed, verified, rejected) is public
did_you_meanNoClose matches to what was asked for: towns, places, slugs or brands, best first
resolved_fromNoSet 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.0
    • addedInput schema / properties / fact
      Added value: +{
      +  "description": "What kind of rule is wrong, if clear. Shown on the public ticket; the message is not.",
      +  "enum": [
      +    "dogs_allowed",
      +    "leash",
      +    "fee",
      +    "weight_or_size_limit",
      +    "number_of_pets",
      +    "breed_rule",
      +    "hours",
      +    "areas",
      +    "closed_or_moved",
      +    "other"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / accepted
      Added value: +{
      +  "additionalProperties": {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "description": "With bad_input: each argument that could not be read, with the values it accepts",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / resolved_from
      Added value: +{
      +  "additionalProperties": {
      +    "additionalProperties": {},
      +    "properties": {
      +      "asked": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          }
      +        ]
      +      },
      +      "used": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          }
      +        ]
      +      }
      +    },
      +    "required": [
      +      "asked",
      +      "used"
      +    ],
      +    "type": "object"
      +  },
      +  "description": "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",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / status_url
      Added value: +{
      +  "description": "Where the ticket's status (filed, verified, rejected) is public",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / ticket
      Added value: +{
      +  "description": "Public ticket id (c-xxxxxxxx) once filed; null otherwise",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Changed8 schema fields changedv0.4.0
    • addedOutput schema / properties / code
      Added value: +{
      +  "description": "With an outcome other than ok: not_found, invalid, unavailable",
      +  "type": "string"
      +}
    • addedOutput schema / properties / did_you_mean
      Added value: +{
      +  "description": "Close matches to what was asked for: towns, places, slugs or brands, best first",
      +  "items": {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / form_url
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / message
      Added value: +{
      +  "description": "What happened, in a sentence",
      +  "type": "string"
      +}
    • addedOutput schema / properties / nearest
      Added value: +{
      +  "description": "When nothing is inside the radius: the nearest places in the data, with distance_miles",
      +  "items": {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / next
      Added value: +{
      +  "description": "Calls that would answer the question, in words",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / outcome
      Added value: +{
      +  "description": "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.",
      +  "enum": [
      +    "ok",
      +    "partial",
      +    "no_match",
      +    "bad_input",
      +    "unavailable"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / status / description
      Added value: +"filed, or not_sent with form_url to file it by hand"
  3. First observedv0.2.0

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only say readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true; the description goes much further, explaining that a human re-reads the official source, that the record does not change until verified, and that 'a report is filed, not a fix'. It also discloses the output contract (ticket id, status_url) and the privacy boundary (status public, message not, no other personal detail accepted) — none of which the annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded in the first sentence, and the follow-up sentences each carry distinct payload (write-path exclusivity, human verification, inputs, return shape). It is dense and slightly long, but no sentence is pure filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write tool with an output schema, everything an agent needs is present: when to fire it, what the fields mean, what happens after submission, and what the caller gets back. The privacy constraint and the public/private split on the ticket are exactly the details that would otherwise cause misuse.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: place_id must come from a result, message is in the traveler's own words, fact is the kind of rule at issue, source_url is the official page, and contact is only captured if offered. The explicit statement that no other personal detail is accepted is a semantic constraint absent from the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and resource ('Tell us a rule is wrong', 'report a correction') and immediately scopes it as 'the one tool that writes', which cleanly separates it from the sixteen read-oriented siblings. The examples (fee went up, beach closed, hotel takes two pets) make the resource unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the triggering condition clearly ('For a record the traveler says is wrong or out of date') and effectively excludes all siblings by declaring this the only write path. It stops short of naming a read alternative for a traveler who merely wants to look something up, so routing for that case is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.