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

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)
`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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 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, Toronto, Ottawa)"New value: +"rank by drive time from this city (Vancouver, Victoria, Nanaimo, Whistler, Kelowna, Kamloops, Cranbrook, Prince George, Fort St. John)"

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.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it uses the default tent-compatible inventory, can filter confirmed amenities, and ranks results by soonest opening or drive time. This helps the agent understand result semantics without contradicting the annotations.

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?

Three sentences with no filler: use case and examples first, then default behavior, then clear exclusions with alternatives. Every sentence adds decision-relevant information and the most important scoping constraint is front-loaded.

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?

The description fully covers when to use the tool, when not to use it, and which alternatives to choose. With an output schema present and detailed input schema descriptions, an agent has everything needed to select and invoke the tool correctly. No critical context is missing.

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 90%, so most parameters are already well documented in the schema. The description adds useful context like default tent-compatible inventory and confirmed amenities, but it does not explain individual parameters beyond what the schema provides. Baseline 3 is appropriate because the schema carries the parameter-documentation burden.

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 states a specific action: finding parks ranked by soonest opening or estimated drive time when no park is named. It explicitly distinguishes itself from siblings by defining its scope (unnamed park, ranked results, default tent-compatible inventory), so an agent can select it without inspecting other 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?

It gives explicit when-to-use guidance with concrete user examples, and states when not to use it: when equipment fit matters or when a specific park is named. It names the exact alternatives (parksopen_search_campsites with equipment_class, parksopen_park_availability_calendar), leaving no ambiguity.

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?