Parks Open

Forecast and air quality at a park

parksopen_check_weather

Read-onlyIdempotent

Use this when the user asks about forecast conditions or air quality at a named park. It returns the Environment Canada forecast (daily high/low/conditions, about 6 days) and AQHI for the nearest station; if the park is beyond range it says so and never invents temperatures.

Input Schema

TableJSON Schema

Name	Required	Description
`park`	Yes	park name
`system`	No	reservation system id, e.g. bc_parks. Omit for the default system.
`province`	No	province code or URL prefix (bc, on, …) — an alternative to system.

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": {
+        "park": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "weather": {
+          "anyOf": [
+            {
+              "additionalProperties": false,
+              "properties": {
+                "aqhi": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "city": {
+                  "type": "string"
+                },
+                "currentTemp": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "days": {
+                  "items": {
+                    "additionalProperties": false,
+                    "properties": {
+                      "condition": {
+                        "type": "string"
+                      },
+                      "date": {
+                        "type": "string"
+                      },
+                      "high": {
+                        "type": [
+                          "number",
+                          "null"
+                        ]
+                      },
+                      "icon": {
+                        "type": "string"
+                      },
+                      "label": {
+                        "type": "string"
+                      },
+                      "low": {
+                        "type": [
+                          "number",
+                          "null"
+                        ]
+                      },
+                      "pop": {
+                        "type": [
+                          "number",
+                          "null"
+                        ]
+                      }
+                    },
+                    "required": [
+                      "date",
+                      "label",
+                      "high",
+                      "low",
+                      "icon",
+                      "condition",
+                      "pop"
+                    ],
+                    "type": "object"
+                  },
+                  "type": "array"
+                },
+                "updated": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "required": [
+                "city",
+                "updated",
+                "currentTemp",
+                "days",
+                "aqhi"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "park",
+        "weather"
+      ],
+      "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

Behavior5/5

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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint), the description discloses the data source (Environment Canada), the format (daily high/low/conditions, about 6 days), the AQHI from nearest station, and the honest behavior of saying when out of range and never inventing temperatures. This adds substantial behavioral context beyond the annotations.

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?

The description is a single, front-loaded sentence that packs the trigger condition, the output content, and an edge-case guarantee without waste. Every clause adds value, making it concise and well-structured.

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?

The description covers the core purpose, data source, output scope, and a key edge case (out-of-range handling). An output schema exists to define the return structure, so the description doesn't need to repeat that. It is complete for a low-complexity tool, though it doesn't mention error handling for invalid park names, which is a minor gap.

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 coverage is 100%, so the input schema already documents all three parameters (park, system, province) with descriptions. The tool description adds no extra parameter-level detail beyond what the schema provides, so it meets the baseline of 3 but does not exceed it.

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 (check forecast and air quality) on a specific resource (named park), and clearly distinguishes from siblings like check_alerts or park_info. The trigger condition is explicit: 'Use this when the user asks about forecast conditions or air quality at a named park.'

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 description gives a clear when-to-use trigger ('when the user asks about forecast conditions or air quality at a named park'), but does not explicitly mention when not to use it or name alternative tools. It implies the scope well but lacks an explicit exclusion or alternative routing.

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?