Skip to main content
Glama
DogPolicies MCP Server

DogPolicies MCP Server

by xultrax-web

Changes since a date

dogpolicies_changes_since
Read-onlyIdempotent

List changes to dog rules since a given date—fees, leash rules, closures, and source status—to poll updates without re-reading records.

Instructions

What changed in the dog rules anywhere since a date: which fees, leash rules or closures were updated or found gone? A cheap poll for new changes across all the data, without re-reading records. Input: since as YYYY-MM-DD; optional outcome (confirmed, changed, source_gone, blocked, disputed), for example "changed" for only real rule changes. Returns events newest first, each naming the place, what happened, who checked, the date and a link to the record. On the hosted server a separate corrections list shows corrections people filed or whose status changed since the date: ticket id, place, kind of fact, status (filed, verified, rejected), dates and a status_url; what the reporter wrote is never included.

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": {
      "since": "<since>"
    },
    "name": "dogpolicies_changes_since"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return
sinceYesDate, YYYY-MM-DD
offsetNoResults to skip, for pagination
outcomeNoOnly events with this outcome
response_formatNo'markdown' for readable text, 'json' for structured datamarkdown

Output Schema

NameRequiredDescriptionDefault
as_ofYesDate the data was built (YYYY-MM-DD)
countYes
totalYes
eventsYes
licenseYes
has_moreYes
correctionsNoCorrections people filed or whose status changed in the window (the hosted server only), newest first
rule_changesYes
attribution_urlYes
attribution_textYes
corrections_noteNoWhy corrections is empty when this server cannot list them
corrections_totalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • addedOutput schema / properties / corrections
      Added value: +{
      +  "description": "Corrections people filed or whose status changed in the window (the hosted server only), newest first",
      +  "items": {
      +    "additionalProperties": {},
      +    "properties": {
      +      "changed_at": {
      +        "description": "When the status last changed",
      +        "type": "string"
      +      },
      +      "decided_at": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "fact": {
      +        "description": "Kind of fact, or unspecified",
      +        "type": "string"
      +      },
      +      "filed_at": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "place_id": {
      +        "type": "string"
      +      },
      +      "place_name": {
      +        "type": "string"
      +      },
      +      "reason": {
      +        "description": "For a rejection: not_supported_by_source, duplicate, out_of_scope, could_not_verify or spam",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "status": {
      +        "description": "filed, verified or rejected",
      +        "type": "string"
      +      },
      +      "status_url": {
      +        "type": "string"
      +      },
      +      "ticket": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "ticket",
      +      "place_id",
      +      "place_name",
      +      "fact",
      +      "status",
      +      "filed_at",
      +      "decided_at",
      +      "changed_at",
      +      "reason",
      +      "status_url"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / corrections_note
      Added value: +{
      +  "description": "Why corrections is empty when this server cannot list them",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / corrections_total
      Added value: +{
      +  "type": "number"
      +}
  2. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description adds genuinely new context: results are newest first, each event carries place/what/who/date/link, and a hosted-server-only corrections list appears with a privacy guarantee that reporter text is never included. That said, with an output schema present and annotations covering the safety profile, much of the return-field detail overlaps structured data, so the net addition is moderate rather than rich.

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?

Well front-loaded: purpose, cost rationale, inputs, then outputs. The final sentence about the corrections list is long and dense with field names, but every clause carries information an agent would otherwise lack, so waste is minimal.

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 five-parameter read tool with an output schema, the definition covers purpose, filtering semantics, result ordering, per-event contents, and a server-environment caveat (corrections list only on the hosted server). An agent has everything needed to call it and interpret the response without further guessing.

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 meaning beyond the schema: it restates 'since' must be YYYY-MM-DD and, more usefully, interprets the outcome enum with a concrete example ('changed' for only real rule changes). limit/offset/response_format are left entirely to the schema, which is acceptable at full coverage.

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

Purpose4/5

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

The opening line names a specific verb and resource ('what changed in the dog rules anywhere since a date') and enumerates the kinds of changes (fees, leash rules, closures). The word 'anywhere' implicitly contrasts with a place-scoped sibling, but no sibling is named, so differentiation is left to inference.

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 explicitly frames the tool as 'a cheap poll for new changes across all the data, without re-reading records', which tells the agent when this is the economical choice. It gives an example filter ('changed' for only real rule changes) but never states when not to use it or names the alternative tool.

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