Parks Open

Check BC Parks day-pass availability

parksopen_check_day_passes

Read-onlyIdempotent

Use this when the user asks whether a BC Parks day-use pass is required, available, sold out, not released yet, or closed for a date, park, access area, or AM/PM slot. It returns the access areas currently covered by live checks across a three-day booking window, with explicit No pass needed versus Sold out states, freshness, coverage limits, the Parks Open comparison page, and the official BC Parks booking handoff. If live inventory is stale, incomplete, or conflicts with published rules, it fails closed and will not claim Available or Sold out.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	visit date, YYYY-MM-DD. Omit for today in British Columbia.
`days`	No	number of consecutive dates to compare, 1 to 3; default is the full 3-day booking window
`parks`	No	optional park names, e.g. ['Golden Ears', 'Garibaldi']; omit to return every tracked day-pass park

Output Schema

TableJSON Schema

Name	Required	Description	Default
`to`	Yes
`from`	Yes
`live`	Yes
`note`	Yes
`page`	Yes
`parks`	Yes
`freshness`	Yes
`booking_url`	Yes
`observed_at`	Yes
`suggestions`	Yes
`coverage_through`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

changedOutput schema / properties / freshness / enum

Previous value: -[
-  "ok",
-  "no-database",
-  "no-data",
-  "incomplete",
-  "conflict",
-  "stale",
-  "error"
-]New value: +[
+  "ok",
+  "no-database",
+  "no-data",
+  "incomplete",
+  "conflict",
+  "stale",
+  "unknown",
+  "error"
+]

AddedSep 17, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld), the description discloses fail-closed behavior under stale/conflicting data, freshness, coverage limits, the comparison page, and the booking handoff. This is rich behavioral context an agent could not infer from structured fields.

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-loads the usage trigger, then packs return states, coverage limits, and the fail-closed guarantee into dense sentences with little waste. Slightly long, but every clause carries signal.

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 values need not be explained, yet the description still conveys the key states, freshness, coverage limits, and the fail-closed guarantee. Nothing needed to call this correctly 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 100%, so the schema already documents date, days, and parks, including defaults and bounds. The description adds only the three-day booking-window framing, and mentions 'access area' and 'AM/PM slot' which are not parameters, 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?

States a specific verb+resource (check BC Parks day-pass availability) and enumerates the exact question states it answers (required, available, sold out, not released, closed). It is clearly distinguishable from siblings like parksopen_search_campsites or parksopen_check_alerts.

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

Usage Guidelines4/5

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

The opening 'Use this when the user asks whether...' gives explicit trigger conditions covering date, park, access area, and AM/PM slot. It does not, however, name a sibling alternative or state when-not to use it, so it stops short of a 5.

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?