Parks Open

Park facts, rules and fees (knowledge base)

parksopen_park_info

Read-onlyIdempotent

Use this when the user asks about reservation policy, fees, pets, fires, facilities, or park descriptions, such as 'does X allow dogs' or 'when do reservations open'. Verified policy knowledge currently covers BC Parks only; other systems return an explicit unsupported answer with the official source. Specify system or province for general policy questions; without a park or system the scope is BC Parks. Do not use it for availability (parksopen_search_campsites) or current closures (parksopen_check_alerts).

Input Schema

TableJSON Schema

Name	Required	Description
`park`	No	park name, when the question is about one park
`system`	No	reservation system id, e.g. bc_parks
`province`	No	province code or prefix, e.g. bc
`question`	Yes	what you want to know (fees, pets, fires, showers, reservations policy…)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 6, 2026

addedInput schema / properties / province

Added value: +{
+  "description": "province code or prefix, e.g. bc",
+  "type": "string"
+}

addedInput schema / properties / system

Added value: +{
+  "description": "reservation system id, e.g. bc_parks",
+  "type": "string"
+}

removedOutput schema / additionalProperties
```
Removed value: -false
```

addedOutput schema / anyOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "context": {
+        "type": "string"
+      },
+      "note": {
+        "type": "string"
+      },
+      "park": {
+        "anyOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "name": {
+                "type": "string"
+              },
+              "slug": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "slug",
+              "name"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "sources": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "park",
+      "context",
+      "sources",
+      "note"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "error": {
+        "type": "string"
+      },
+      "suggestions": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties

Removed value: -{
-  "context": {
-    "type": "string"
-  },
-  "note": {
-    "type": "string"
-  },
-  "park": {
-    "anyOf": [
-      {
-        "additionalProperties": false,
-        "properties": {
-          "name": {
-            "type": "string"
-          },
-          "slug": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "slug",
-          "name"
-        ],
-        "type": "object"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "sources": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "park",
-  "context",
-  "sources",
-  "note"
-]

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": {
+    "context": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "park": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "slug": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "slug",
+            "name"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "sources": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "park",
+    "context",
+    "sources",
+    "note"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: verified policy coverage is limited to BC Parks, other systems return an explicit unsupported answer with an official source, and the default scope falls back to BC Parks. It does not discuss answer length or formatting, but the coverage limit and fallback are the important disclosures.

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 dense sentences, front-loaded with the use case, then coverage caveat, then routing exclusions. Every clause carries decision-relevant information with no 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 explanation is unnecessary. Given four optional params at full schema coverage and rich annotations, the description supplies the remaining gaps — coverage limits, default scope, and sibling routing — making it complete for correct invocation.

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 description coverage is 100%, so the baseline is 3, but the description adds selection semantics the schema lacks: specify system or province for general policy questions, and omitting park/system defaults the scope to BC Parks. That is a real rule about how the optional parameters interact, not a restatement.

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 knowledge-base retrieval purpose with concrete topic coverage (reservation policy, fees, pets, fires, facilities) and example questions. The title and description together make it unmistakable versus the availability and alerts siblings.

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 both when-to-use ('user asks about reservation policy, fees, pets...') and explicit exclusions routing to parksopen_search_campsites for availability and parksopen_check_alerts for closures. It even names the sibling tools for those cases, leaving nothing 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?