Skip to main content
Glama

Parks Open

by ca.parksopen

Forecast and air quality at a park

parksopen_check_weather
Read-onlyIdempotent

Environment Canada forecast (daily high/low/conditions, ~6 days) and AQHI for the station nearest a park. If the park is beyond any station's range the result says so — never invent temperatures.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parkYespark name
systemNoreservation system id, e.g. bc_parks. Omit for the default system.
provinceNoprovince code or URL prefix (bc, on, …) — an alternative to system.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

The description adds strong behavioral context beyond the annotations: it names the data source, states the forecast horizon, explains the nearest-station logic, and explicitly promises not to invent temperatures when a park is out of range. This goes well beyond the readOnly/idempotent hints.

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?

Two dense, front-loaded sentences deliver the core output, data source, time range, and an important edge-case guarantee with zero filler. Every sentence earns its place.

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?

With no output schema, the description still adequately conveys what the response will contain and how out-of-range cases behave. Combined with 100% parameter coverage and a simple one-required-parameter input shape, no essential context is missing for an agent to invoke the tool correctly.

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 baseline is 3. The description reinforces the result scope but adds no new meaning about the park, system, or province parameters beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool's purpose: retrieving Environment Canada forecast data and AQHI for the station nearest a park. It states specific output content (daily high/low/conditions, ~6 days) and distinguishes the weather use case from sibling tools by its explicit resource focus, though it does not explicitly name sibling alternatives.

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

Usage Guidelines3/5

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

Usage context is implied through the description: use this tool when an agent needs forecast or air quality information for a park. However, there is no explicit guidance about when not to use it or how it compares to sibling tools such as parksopen_check_alerts or parksopen_park_info.

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

All Parks Open toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

The tools are mostly distinct: alerts, weather, park info, booking links, and availability each target clear concerns. The only real overlap risk is parksopen_find_open_parks vs parksopen_search_campsites, since both can answer 'which parks have openings', though their descriptions try to separate the no-specific-park vs specific-dates/equipment cases.

Naming Consistency4/5

All tools share the parksopen_ prefix and use snake_case, which helps. Most follow a verb_noun pattern (check_alerts, check_weather, find_open_parks, get_booking_link, search_campsites), but parksopen_park_availability_calendar and parksopen_park_info are noun-first deviations, making the set slightly less predictable.

Tool Count5/5

Seven tools is well-scoped for a camping/reservation assistant: search, find, calendar, alerts, weather, info, and booking link cover the main user journey without bloat. Each tool appears to earn its place.

Completeness5/5

The tool surface covers the full assisted workflow: discovering open parks, checking live availability for dates, viewing multi-week calendars, retrieving park rules and fees, checking alerts and weather, and generating booking links. The explicit decision not to book on the user's behalf is handled through parksopen_get_booking_link, so no critical lifecycle step is missing.

Resources