Skip to main content
Glama
Bigred97

au-weather-mcp

describe_location

Resolve any Australian location to its precise coordinates, timezone, elevation, and nearest BOM station. Use it to verify location before fetching weather data.

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
descriptionNo
latitudeYes
longitudeYes
timezoneYes
elevation_mNo
nearest_bom_stationNo
open_meteo_urlYes
attributionYes
Behavior5/5

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

The description discloses behavioral traits comprehensively: input shape flexibility, case-insensitivity, conditional id (None for non-curated, snake_case key for curated), and mentions returned LocationDetail structure. With no annotations, the description fully covers behavioral expectations.

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 with clear sections: purpose, input behavior, usage, and return. It is concise despite length, with no redundant information. Front-loaded purpose and examples are effective.

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 the complexity of input, presence of output schema, and 100% schema coverage, the description is complete. It covers all aspects needed for correct tool usage, including return values (detailed in output schema) and usage context.

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?

Although schema coverage is 100%, the description adds significant value beyond the schema by explaining the various input shapes, case-insensitivity, and providing multiple examples. It clarifies how the parameter is interpreted, which the schema alone does not convey.

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 clearly states the tool returns metadata for an Australian location, listing specific fields like name, lat/lng, timezone, elevation, and BOM station ID. It distinguishes itself from siblings by explicitly mentioning its use before get_weather and for cross-referencing.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use scenarios: before calling get_weather, to confirm coordinates/timezone, to cross-reference with BOM, and to verify ambiguous input. It implies usage context and alternative tools (get_weather).

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