Skip to content

Fix get_weather docstring: wind -> wind_speed - #100

Merged
vedaant00 merged 1 commit into
mldsveda:mainfrom
Girdharilal-aiml:fix-weather-docstring
Aug 5, 2026
Merged

Fix get_weather docstring: wind -> wind_speed#100
vedaant00 merged 1 commit into
mldsveda:mainfrom
Girdharilal-aiml:fix-weather-docstring

Conversation

@Girdharilal-aiml

Copy link
Copy Markdown
Contributor

Fixes #95

Changed the get_weather docstring to correctly list wind_speed instead of wind to match the actual scraper output.

@vedaant00
vedaant00 requested a lite review from Copilot August 5, 2026 10:21
@vedaant00
vedaant00 merged commit f819aa3 into mldsveda:main Aug 5, 2026
6 checks passed

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the MCP get_weather tool documentation so it matches the weather scraper’s emitted field name (wind_speed), preventing clients from relying on a non-existent wind key.

Changes:

  • Update get_weather docstring to advertise wind_speed instead of wind.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +441 to 442
"""Fetch the current weather conditions for a named place and return a dict with keys: temperature (number, degrees Celsius), humidity (number, percent), wind_speed (number, wind speed), condition (str, e.g. "Clear", "Rain"), and location (str, the resolved place name).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

get_weather docstring promises a 'wind' key but the scraper emits 'wind_speed'

3 participants