Skip to main content
Glama
BACH-AI-Tools

Weather API167 MCP Server

current_weather

Get current weather conditions for any location using coordinates, city name, or zip code. Returns temperature, humidity, wind speed, and more in your chosen units and language.

Instructions

Fetch current weather data using coordinate value, place name or zip code

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lonNoLongitude coordinate(Note. lat and lon value has priority over both place and zip value). use the lat and lon for more accurate and reliable weather data0
latNoLatitude coordinate(Note. lat and lon value has priority over both place and zip value). use the lat and lon for more accurate and reliable weather data0
placeNoCity name, state code (only for the US) and country code divided by comma use like Zion,VA,US . Please use ISO 3166 country codes. Note. place value has priority over zip value
zipNoZip code with optional country code(Note. Zip value will only be used if both lat,lon and place name not provided)
unitsNoUnit type (standard, metric, and imperial)
langNoLanguage type
modeNoMode type
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention data freshness, rate limits, authentication, or response format. The tool's behavior beyond fetching is opaque, limiting transparency.

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 a single, clear sentence of 12 words that directly states the tool's action and inputs. Every word contributes meaning, with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 7 parameters and no output schema, the description should explain what data is returned (e.g., temperature, humidity) and clarify behavior for missing inputs. It only mentions location methods, leaving significant gaps for an agent to understand the tool fully.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description reiterates the three location methods but adds no new meaning beyond the schema's detailed parameter descriptions. There is no benefit or penalty beyond baseline.

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 fetches 'current weather data' using specific location methods (coordinate, place, zip). This distinguishes it from sibling tools like 'forecast_weather' and 'air_pollution_data', providing a clear purpose.

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 outlines three location input methods but does not explicitly state when to prefer this tool over siblings. However, the sibling names (e.g., 'forecast_weather', 'air_pollution_data') imply differentiation, and the schema elaborates on parameter priority.

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/BACH-AI-Tools/weather_api167'

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