Skip to main content
Glama
Bigred97

au-weather-mcp

describe_location

Retrieve detailed metadata for any Australian location including coordinates, timezone, and elevation. Accepts place names, state codes, or raw coordinates to resolve ambiguous input before weather lookups.

Instructions

Return metadata for an Australian location — name, lat/lng, timezone, elevation, and (for curated locations) the nearest BOM station ID.

Accepts a wide range of input shapes for compatibility — see the location parameter description. The returned id is None for non-curated lookups (geocoded place names, raw coordinates) and a snake_case curated key when the input matched the curated set.

Examples: await describe_location("sydney") # → curated path await describe_location("Sydney") # → curated path (case-insensitive) await describe_location("NSW") # → state capital (Sydney) await describe_location("Margaret River") # → geocoded (Western Australia) await describe_location("-33.87,151.21") # → raw coordinates

When to use: - Before calling get_weather, to confirm coordinates and timezone - To cross-reference with BOM's own observation network (for curated) - To verify how the server resolved an ambiguous customer input

Returns: LocationDetail with id (or None), name, state, lat/lng, timezone, elevation, nearest BOM station ID (curated only), the Open-Meteo URL, and the CC-BY attribution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationYesAny Australian location, in any of these shapes: (1) curated ID like 'sydney', 'gold_coast'; (2) place name in any case like 'Sydney', 'Gold Coast', 'Margaret River', 'Byron Bay'; (3) state code or name like 'NSW', 'VIC', 'Queensland' (returns the state capital); (4) raw coordinates like '-33.87,151.21'. Case-insensitive throughout.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameYes
stateYes
latitudeYes
timezoneYes
longitudeYes
attributionYes
descriptionNo
elevation_mNo
open_meteo_urlYes
nearest_bom_stationNo
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that input can be various shapes (curated IDs, place names, states, coordinates), explains the behavior of the returned 'id' (None for non-curated, snake_case for curated), and mentions case-insensitivity. It lacks an explicit read-only declaration but implies a safe lookup.

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 well-structured and concise: it starts with a clear purpose, then covers input flexibility, return behavior, examples, usage guidance, and return fields. Every sentence adds value without redundancy, achieving a balance between completeness and brevity.

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 that an output schema exists, the description appropriately covers the key return fields (LocationDetail with id, name, state, lat/lng, timezone, elevation, BOM station ID, Open-Meteo URL, attribution). It also addresses non-curated vs. curated behavior and provides usage context, making it complete for the tool's purpose.

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

Parameters5/5

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

Schema description coverage is 100% (the 'location' parameter is well-documented). The description adds significant value beyond the schema by providing multiple examples illustrating different input shapes, explaining the relationship between input and output (especially the 'id' behavior), and clarifying case-insensitivity.

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 explicitly states 'Return metadata for an Australian location' with a specific verb and resource, listing fields like name, lat/lng, timezone, elevation, and BOM station ID. It clearly distinguishes itself from sibling tools (e.g., get_weather, search_locations) by focusing on metadata lookup, not weather or search.

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 includes a 'When to use:' section with three concrete scenarios: before get_weather, for BOM cross-reference, and to verify ambiguous input. While it doesn't explicitly state when not to use, the positive guidance is clear and sufficient for an agent to recognize appropriate contexts.

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