Parks Open

Find parks with openings (ranked)

parksopen_find_open_parks

Read-onlyIdempotent

Use this when the user has not named a park and wants PARKS ranked by soonest opening or estimated drive time, such as 'where can I camp this weekend' or 'anything near Vancouver with space'. It uses the default tent-compatible inventory and can filter confirmed amenities. Do not use it when van, trailer, RV, or other equipment fit matters; use parksopen_search_campsites with equipment_class. For a named park use parksopen_search_campsites or parksopen_park_availability_calendar.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`nights`	No	default 2 (weekend) or 1
`region`	No	restrict to a region name as the site shows it, e.g. 'Vancouver Island'
`system`	No	reservation system id, e.g. bc_parks. Omit for the default system.
`weekend`	No	this coming weekend (Fri→Sun, 2 nights)
`province`	No	province code or URL prefix (bc, on, …) — an alternative to system.
`amenities`	No	ANDed site attributes (confirmed-only; the count is a floor)
`near_city`	No	rank by drive time from this city (Vancouver, Victoria, Nanaimo, Whistler, Kelowna, Kamloops, Cranbrook, Prince George, Fort St. John, Toronto, Ottawa)
`start_date`	No	a specific arrival date; omit to find the soonest opening
`horizon_days`	No	how far ahead to look when no date is fixed; default 14

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / near_city / description

Previous value: -"rank by drive time from this city (Vancouver, Victoria, Nanaimo, Whistler, Kelowna, Kamloops, Cranbrook, Prince George, Fort St. John)"New value: +"rank by drive time from this city (Vancouver, Victoria, Nanaimo, Whistler, Kelowna, Kamloops, Cranbrook, Prince George, Fort St. John, Toronto, Ottawa)"

Changed1 schema field changedSep 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "amenities_applied": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "horizon_days": {
+          "type": "number"
+        },
+        "nights": {
+          "type": "number"
+        },
+        "note": {
+          "type": "string"
+        },
+        "observed_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "parks": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "drive_min": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "earliest_date": {
+                "type": "string"
+              },
+              "earliest_offset_days": {
+                "type": "number"
+              },
+              "ferry": {
+                "type": "boolean"
+              },
+              "page": {
+                "type": "string"
+              },
+              "park": {
+                "type": "string"
+              },
+              "region": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "sites_open": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "park",
+              "page",
+              "region",
+              "earliest_date",
+              "earliest_offset_days",
+              "sites_open",
+              "drive_min",
+              "ferry"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "total_with_openings": {
+          "type": "number"
+        },
+        "window": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "nights",
+        "horizon_days",
+        "window",
+        "amenities_applied",
+        "parks",
+        "total_with_openings",
+        "observed_at",
+        "note"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "error": {
+          "type": "string"
+        },
+        "suggestions": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's added value is its disclosure that the tool silently uses a 'default tent-compatible inventory' and that amenity filters are confirmed-only with the count acting as a floor. These are real behavioral caveats an agent could not infer from the schema. It does not cover pagination or result-size behavior, so it falls 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.

Conciseness5/5

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

Front-loaded with the positively-selecting use case, then the exclusion, then the named-park fallback. Every sentence routes the agent to a decision; the example utterances earn their space by disambiguating intent.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the description covers scope, default inventory, and routing for all 10 optional parameters. It stops short of explaining how weekend/nights/horizon_days interact when several are supplied, which is the main remaining ambiguity for a tool where every parameter is optional.

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 already 90% (baseline 3), and the description adds semantics the schema does not carry: the implicit tent-compatible inventory constraint on results and the 'confirmed-only, count is a floor' meaning of the amenities filter. It does not clarify the interaction between weekend and start_date or the region vs province vs system choice.

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?

States a specific verb and resource ('PARKS ranked by soonest opening or estimated drive time') and gives concrete user phrasings that map to the tool. It explicitly distinguishes itself from the three sibling tools an agent might otherwise reach for.

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?

Provides explicit when-to-use ('user has not named a park'), when-not-to-use (equipment fit matters), and names the alternative for each branch (parksopen_search_campsites with equipment_class, parksopen_search_campsites / parksopen_park_availability_calendar for a named park). Nothing is left to inference.

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?