Skip to main content
Glama
swwayam
by swwayam

Get Current Weather

get_weather
Read-only

Retrieve current weather for any city, with options for metric or imperial units and optional clothing advice. Handles ambiguous city names by clarifying.

Instructions

Get current weather for a city. If the city name is ambiguous, asks you which one you meant. Optionally returns a what-to-wear tip.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityYesCity name, e.g. 'London' or 'San Francisco'
unitsNoUnit system: metric (°C, km/h) or imperial (°F, mph)metric
includeAdviceNoIf true, ask the host LLM (via MCP sampling) for a short what-to-wear tip

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityYes
countryYes
latitudeYes
longitudeYes
observedAtYesISO timestamp of the observation
unitsYes
temperatureYes
apparentTemperatureYes
humidityYesRelative humidity (%)
windSpeedYes
weatherCodeYesWMO weather interpretation code
conditionsYesHuman-readable condition
temperatureUnitYes
windSpeedUnitYes
adviceNoLLM-generated recommendation (present only if sampling ran)
Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that it can ask for clarification on ambiguous names and optionally include a what-to-wear tip via MCP sampling.

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?

Two sentences cover all essential information without redundancy, making it highly concise and efficiently front-loaded.

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 an output schema exists, the description adequately covers key behaviors (weather retrieval, ambiguity handling, optional advice) and complements the sibling tool differentiation.

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?

With 100% schema coverage, baseline is 3; the description adds meaning by linking the 'city' parameter to disambiguation behavior and the 'includeAdvice' parameter to the optional tip.

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 retrieves current weather for a city, distinguishes itself from sibling 'compare_weather' by focusing on single-city current conditions, and explicitly mentions behavior for ambiguous city names.

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 provides context on when the tool might ask for disambiguation (ambiguous city names), but does not specify when not to use it or alternatives like 'compare_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/swwayam/mcp-weather'

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