Parks Open

Search campsites by live availability

parksopen_search_campsites

Read-onlyIdempotent

Use this when exact dates or equipment fit matter, for questions like 'is X available', 'find a site for the long weekend', or 'which parks have space for a 32 ft RV'. It reads observed campsite availability for BC Parks and limited Ontario Parks coverage (15 reservation locations, frontcountry camping only). Ontario camping alerts are not enabled. Filters the official sites cannot: exact equipment fit, electrical, waterfront, shade, pets, privacy — across every park at once. Returns only sites observed open for EVERY requested night, with an absolute Parks Open page URL to cite, a booking link into the official reservation flow (we never book for the user), and observed_at for freshness; verify availability on the official site. Not for: fees, rules, facilities (use parksopen_park_info), weather (parksopen_check_weather), closures (parksopen_check_alerts), or dates beyond the provider's booking window.

Input Schema

TableJSON Schema

Name	Required	Description
`park`	No	park name — approximate is fine (partial, missing 'Provincial', misspelled). Omit to search every park. If it cannot be resolved you get a did-you-mean list.
`limit`	No	page size, default 20
`cursor`	No	opaque cursor from a previous page
`system`	No	reservation system id, e.g. bc_parks. Omit for every tracked system.
`category`	No	booking category; default frontcountry (drive-in campsites)
`end_date`	Yes	departure, YYYY-MM-DD (exclusive; nights = end − start)
`province`	No	province code or URL prefix (bc, on, …) — an alternative to system.
`amenities`	No	ANDed site attributes: electrical, waterfront, pets, some_shade, full_shade, double, near_restroom, walk_in, accessible, pull_through, private, big_rig
`start_date`	Yes	arrival, YYYY-MM-DD
`min_privacy`	No	'Good' or 'Excellent'
`equipment_class`	No	canonical class (tent, tent2, tent3, van, trailer_18, rv_32, rv_32_plus) or free text like '30ft trailer'. Default tent.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes
`total`	Yes
`nights`	Yes
`closure`	Yes
`results`	Yes
`next_cursor`	Yes
`observed_at`	Yes
`suggestions`	Yes
`resolved_park`	Yes
`equipment_class`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "closure": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "park": {
+              "type": "string"
+            },
+            "source": {
+              "type": "string"
+            },
+            "title": {
+              "type": "string"
+            },
+            "until": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "park",
+            "title",
+            "until",
+            "source"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "equipment_class": {
+      "type": "string"
+    },
+    "next_cursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "nights": {
+      "type": "number"
+    },
+    "note": {
+      "type": "string"
+    },
+    "observed_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "resolved_park": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "attributes": {
+            "additionalProperties": false,
+            "properties": {
+              "adjacent": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "electrical": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "privacy": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "shade": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "privacy",
+              "shade",
+              "electrical",
+              "adjacent"
+            ],
+            "type": "object"
+          },
+          "booking_url": {
+            "type": "string"
+          },
+          "fit": {
+            "type": "string"
+          },
+          "loop": {
+            "type": "number"
+          },
+          "nights": {
+            "type": "number"
+          },
+          "page": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "park": {
+            "type": "string"
+          },
+          "park_key": {
+            "type": "string"
+          },
+          "site_id": {
+            "type": "number"
+          },
+          "slug": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "system": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "system",
+          "park",
+          "park_key",
+          "slug",
+          "page",
+          "site_id",
+          "loop",
+          "nights",
+          "fit",
+          "attributes",
+          "booking_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "suggestions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "results",
+    "total",
+    "next_cursor",
+    "nights",
+    "equipment_class",
+    "resolved_park",
+    "suggestions",
+    "observed_at",
+    "closure",
+    "note"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations cover safety (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, yet the description adds substantial operational context: coverage limits (BC Parks + 15 Ontario locations, frontcountry only), disabled Ontario alerts, 'we never book for the user', observed_at freshness, and the verify-on-official-site caveat. It doesn't cover pagination behavior or rate limits, keeping it just short of a 5.

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?

Front-loaded with trigger and scope before pivoting to capability, return shape, then exclusions — a logical order. It is dense and long for a single paragraph, but nearly every clause carries information; the 'Not for' list is compact and high-value rather than 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?

An output schema exists so return-value detail isn't required, yet the description still summarizes the return (only sites open every night, citable URL, booking link, observed_at). Combined with coverage limitations, provider-window caveat, and sibling routing, an agent has everything needed to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents park resolution, dates, limit/cursor, system/province, category, amenities and equipment_class. The description reinforces the filter concepts (equipment fit, electrical, waterfront, shade, pets, privacy) but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

Starts with a specific verb+resource ('Search campsites by live availability') and immediately scopes it ('exact dates or equipment fit'). The examples ('is X available', '32 ft RV') make the intent unmistakable and differentiate it from the sibling availability/park tools.

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

Usage Guidelines5/5

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

Gives explicit when-to-use triggers, concrete question patterns, and a full 'Not for:' list routing fees/rules to parksopen_park_info, weather to parksopen_check_weather, and closures to parksopen_check_alerts. Alternatives and exclusions are both named.

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

All Parks Open tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?