Skip to main content
Glama

Sitesy Website Intelligence

Canada weather bundle

weather_canada
Read-onlyIdempotent

Official Canadian weather in one call: current conditions, daily and hourly forecast, active alerts, and the Air Quality Health Index, from Environment and Climate Change Canada under the Open Government Licence (Canada). Give a place name, a site code, or lat and lon. Costs 0.001 USDC per call. The caller pays per call in USDC on Base through x402: the first call returns the payment requirements, and an x402 aware MCP client signs and retries automatically.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "weather_canada"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoCanadian place name, English or French, for example Hamilton
latNoLatitude, used with lon
lonNoLongitude, used with lat
langNoLanguage, en by default
siteNoECCC site code, for example s0000549

Output Schema

NameRequiredDescriptionDefault
dailyYes
alertsYes
hourlyYes
currentYes
partialNo
locationYes
air_qualityYes
attributionYes
generated_utcYes
forecast_issue_utcNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the description goes beyond them usefully: it discloses a per-call cost of 0.001 USDC, the x402 payment flow on Base, and that the first call returns payment requirements requiring a signed retry. That is exactly the non-obvious behavior an agent must know to avoid treating a 402 as a failure.

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?

Content is front-loaded: what you get, then how to specify location, then cost and payment mechanics. Every sentence carries information, though the x402 explanation takes two clauses where one would do for an already x402-aware client.

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?

An output schema exists, so return values need no explanation, and payment, sourcing, and licensing are all covered. The remaining gap is locator parameter interaction for a tool with zero required parameters—an agent cannot tell whether calling with no arguments is valid or which locator wins.

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 explains q, lat, lon, lang, and site individually including ranges and examples. The description only restates the location modes at a high level and adds nothing about precedence, mutual exclusivity, or the en/fr language parameter. 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?

The description names a specific verb and resource and enumerates exactly what the bundle returns: current conditions, daily and hourly forecast, active alerts, and AQHI. It also identifies the authoritative source (Environment and Climate Change Canada), which is decisive for a weather tool. Siblings are all web/DNS utilities, so no differentiation is required.

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?

It says the caller can supply a place name, a site code, or lat/lon, which covers the main input decision, and the payment paragraph warns about the first-call 402. However it never states precedence when multiple locators are given, never says what happens when zero of the five optional parameters are supplied, and gives no when-not-to-use guidance.

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