Skip to main content
Glama

Search campsites by live availability

parksopen_search_campsites
Read-onlyIdempotent

Use this when exact dates or equipment fit matter, for questions like 'is X available', 'find a site for the long weekend', or 'which parks have space for a 32 ft RV'. It reads observed campsite availability for BC Parks. Ontario collection is paused; Ontario live inventory and camping alerts are unavailable. Filters the official sites cannot: exact equipment fit, electrical, waterfront, shade, pets, privacy — across every park at once. Returns only sites observed open for EVERY requested night, with an absolute Parks Open page URL to cite, a booking link into the official reservation flow (we never book for the user), and observed_at for freshness; verify availability on the official site. Not for: fees, rules, facilities (use parksopen_park_info), weather (parksopen_check_weather), closures (parksopen_check_alerts), or dates beyond the provider's booking window.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "parksopen_search_campsites"
  }
}

Input Schema

NameRequiredDescriptionDefault
parkNopark name — approximate is fine (partial, missing 'Provincial', misspelled). Omit to search every park. If it cannot be resolved you get a did-you-mean list.
limitNopage size, default 20
cursorNoopaque cursor from a previous page
systemNoreservation system id, e.g. bc_parks. Omit for every tracked system.
categoryNobooking category; default frontcountry (drive-in campsites)
end_dateYesdeparture, YYYY-MM-DD (exclusive; nights = end − start)
provinceNoprovince code or URL prefix (bc, on, …) — an alternative to system.
amenitiesNoANDed site attributes: electrical, waterfront, pets, some_shade, full_shade, double, near_restroom, walk_in, accessible, pull_through, private, big_rig
start_dateYesarrival, YYYY-MM-DD
min_privacyNo'Good' or 'Excellent'
equipment_classNocanonical class (tent, tent2, tent3, van, trailer_18, rv_32, rv_32_plus) or free text like '30ft trailer'. Default tent.

Output Schema

NameRequiredDescriptionDefault
noteYes
totalYes
nightsYes
closureYes
resultsYes
next_cursorYes
observed_atYes
suggestionsYes
resolved_parkYes
equipment_classYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "closure": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": false,
      +          "properties": {
      +            "park": {
      +              "type": "string"
      +            },
      +            "source": {
      +              "type": "string"
      +            },
      +            "title": {
      +              "type": "string"
      +            },
      +            "until": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            }
      +          },
      +          "required": [
      +            "park",
      +            "title",
      +            "until",
      +            "source"
      +          ],
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "equipment_class": {
      +      "type": "string"
      +    },
      +    "next_cursor": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "nights": {
      +      "type": "number"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "observed_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "resolved_park": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "results": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "attributes": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "adjacent": {
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              },
      +              "electrical": {
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              },
      +              "privacy": {
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              },
      +              "shade": {
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              }
      +            },
      +            "required": [
      +              "privacy",
      +              "shade",
      +              "electrical",
      +              "adjacent"
      +            ],
      +            "type": "object"
      +          },
      +          "booking_url": {
      +            "type": "string"
      +          },
      +          "fit": {
      +            "type": "string"
      +          },
      +          "loop": {
      +            "type": "number"
      +          },
      +          "nights": {
      +            "type": "number"
      +          },
      +          "page": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "park": {
      +            "type": "string"
      +          },
      +          "park_key": {
      +            "type": "string"
      +          },
      +          "site_id": {
      +            "type": "number"
      +          },
      +          "slug": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "system": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "system",
      +          "park",
      +          "park_key",
      +          "slug",
      +          "page",
      +          "site_id",
      +          "loop",
      +          "nights",
      +          "fit",
      +          "attributes",
      +          "booking_url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "suggestions": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "results",
      +    "total",
      +    "next_cursor",
      +    "nights",
      +    "equipment_class",
      +    "resolved_park",
      +    "suggestions",
      +    "observed_at",
      +    "closure",
      +    "note"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: Ontario collection is paused, results are only sites observed open for EVERY requested night, it never books, and availability should be verified officially. However, pagination/limits behavior is left entirely to the schema, so it's not maximally rich for an 11-param search tool.

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-loaded with the usage trigger, then coverage caveats, then return shape and exclusions — a logical order with little waste. It is dense and long-winded in places (em-dash chains, the amenities aside), which keeps it just short of a 5.

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?

For a complex, open-world search with an output schema present, the description covers the decision-critical facts: coverage limits (Ontario paused), result semantics (open every night), the no-booking guarantee, freshness via observed_at, and routing to siblings. Nothing an agent needs to call it 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 every parameter including equipment_class, amenities, and date exclusivity is already documented; baseline 3 applies. The description reinforces which params matter ('exact dates or equipment fit', '32 ft RV') but adds no syntax or format detail beyond the schema.

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 ('reads observed campsite availability for BC Parks') and immediately differentiates itself from siblings by listing what it filters that 'the official sites cannot'. An agent can separate it from park_info, check_alerts, check_weather, and park_availability_calendar without opening any schema.

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?

Opens with an explicit when-to-use trigger with concrete example questions ('is X available', 'long weekend', '32 ft RV'), then gives an explicit 'Not for:' list naming each alternative sibling for fees/rules/weather/closures. Exclusions and alternatives are both spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources