Parks Open

Park availability calendar (8 weeks)

parksopen_park_availability_calendar

Read-onlyIdempotent

Use this when the user asks 'when is X free', 'how busy is X', or 'which weekend should I try' for ONE named park. It returns nightly open counts for the next 8 weeks, whole-stay counts for four weekends, fill rate, and booking rules. For exact equipment fit or specific dates across many parks use parksopen_search_campsites.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No
`park`	Yes	park name — approximate is fine
`system`	No	reservation system id, e.g. bc_parks
`province`	No	province code or prefix, e.g. bc

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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",
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "fill_rate_pct": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "nights": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "date": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "open_sites": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "date",
+              "open_sites"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "note": {
+          "type": "string"
+        },
+        "observed_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "page": {
+          "type": "string"
+        },
+        "park": {
+          "type": "string"
+        },
+        "park_key": {
+          "type": "string"
+        },
+        "reservable_sites": {
+          "type": "number"
+        },
+        "rules": {
+          "additionalProperties": false,
+          "properties": {
+            "max_nights": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "min_lead_days": {
+              "type": "number"
+            },
+            "window": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "window",
+            "min_lead_days",
+            "max_nights"
+          ],
+          "type": "object"
+        },
+        "system": {
+          "type": "string"
+        },
+        "weekends": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "end": {
+                "type": "string"
+              },
+              "label": {
+                "type": "string"
+              },
+              "open_for_whole_stay": {
+                "type": "number"
+              },
+              "start": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "start",
+              "end",
+              "label",
+              "open_for_whole_stay"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "system",
+        "park",
+        "park_key",
+        "page",
+        "reservable_sites",
+        "fill_rate_pct",
+        "nights",
+        "weekends",
+        "rules",
+        "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.4/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses result contents: nightly open counts, whole-stay counts for four weekends, fill rate, and booking rules. It is slightly loose about the 8-week window, which the configurable days parameter can extend up to 92 days, but that is a minor semantic wrinkle.

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 short sentences, each earning its place: one for when to use, one for what it returns, and one for the alternative. The trigger phrases are front-loaded and there is no filler.

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?

Given the output schema, the description does not need to enumerate return fields, and it covers scope, trigger, output highlights, and the main alternative. The only substantive gap is the days parameter, whose effect is neither described in the schema nor clearly connected to the '8 weeks' language in the description.

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?

The schema already documents park, system, and province. The description adds usage context for park ('ONE named park') and implies a default time window ('next 8 weeks', 'four weekends'), but it never explains the days parameter or how it affects the calendar range, leaving that parameter largely undocumented.

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 for a bounded resource: 'returns nightly open counts for the next 8 weeks' for 'ONE named park'. It also anchors the trigger phrases ('when is X free', 'how busy is X', 'which weekend should I try'), distinguishing it clearly from sibling tools, especially parksopen_search_campsites.

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 explicitly opens with 'Use this when...' and gives concrete user-query examples. It then names the alternative and the condition for choosing it: 'For exact equipment fit or specific dates across many parks use parksopen_search_campsites.'

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?