Skip to main content
Glama
Bigred97

au-weather-mcp

latest

Retrieve current weather observations for any Australian location using curated names, states, or coordinates. Provides real-time weather context for any query.

Instructions

Return the current weather observation for any Australian location.

Wraps Open-Meteo's /forecast endpoint with current=... parameters and a 15-minute cache TTL (matches Open-Meteo's own update cadence). Use for "what's the weather right now?" — warm-cache latency < 100 ms.

Examples: resp = await latest("sydney") # curated, fast path resp = await latest("Sydney") # case-insensitive resp = await latest("Byron Bay") # geocoded resp = await latest("NSW") # state → Sydney resp = await latest("-33.87,151.21") # raw coordinates

The response's location_resolution field tells the agent how the input was interpreted ('curated', 'state_alias', 'geocoded', 'raw_coordinates', or 'fuzzy_curated').

When to use: - "What's the weather right now in ?" — canonical use case - Multi-city current-conditions dashboards (call once per place) - Anchoring agent conversations to live weather context

Returns: WeatherResponse with current populated, plus location metadata, resolution source, source_url, CC-BY attribution, and server_version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationYesAny Australian location. Accepted shapes: curated ID ('sydney'), place name in any case ('Sydney', 'Byron Bay', 'Margaret River'), state code or name ('NSW', 'Queensland' → returns the capital), or raw coordinates ('-33.87,151.21').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
location_idYes
location_nameYes
stateYes
latitudeYes
longitudeYes
timezoneYes
location_resolutionYes
location_inputYes
queryNo
periodNo
currentNo
hourlyNo
dailyNo
sourceNoOpen-Meteo (aggregates Bureau of Meteorology data under licence)
attributionNoWeather data by Open-Meteo.com (https://open-meteo.com), licensed under CC BY 4.0. Underlying data includes the Australian Bureau of Meteorology (https://www.bom.gov.au) under Open-Meteo's licensing arrangement.
source_urlYes
retrieved_atYes
server_versionYes
staleNo
stale_reasonNo
Behavior4/5

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

Covers cache TTL (15 minutes), data source (Open-Meteo), geocoding behavior, resolution tracking, and attribution. No rate limits or security info, but sufficient with no annotations provided.

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?

Well-structured with clear sections, bullet points, and examples. Every sentence provides value with no fluff.

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?

Given output schema exists, description covers input, output fields, behavioral details, caching, and use cases. Complete for a weather tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema coverage is 100% with good description and examples. Description adds value by explaining accepted shapes, case-insensitivity, state aliasing, and how resolution is output, going beyond 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?

Clearly states 'Return the current weather observation for any Australian location' with specific verb and resource. Examples and usage section distinguish it from siblings like get_weather and describe_location.

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?

Explicit 'When to use' section with three bullet points covering canonical use, multi-city dashboards, and anchoring conversations. Does not mention when not to use or alternatives, but provides strong contextual guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Bigred97/au-weather-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server