Skip to main content
Glama
BACH-AI-Tools

Weather API167 MCP Server

us_weather_alert_data

Retrieve US weather alerts for specific areas, regions, or zones using filters like urgency, severity, certainty, and message type. Get targeted alert data for land or marine regions with optional limit.

Instructions

US weather alert daily information for given region or area and other filtering parameter

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNouse comm(,) to separate multiple value
message_typeNoExample value: alert,update,cancel
areaNoexample AM,AN
regionNoExample value: AL,AT
zoneNoExample>> OKZ929
region_typeNoExample>> marine,land This value can't be used in combination with area or region
urgencyNoExample value: Immediate,Expected
severityNoExample value: Extreme,Severe,Moderate
certaintyNoExample value: Observed,Likely,Possible,Unlikely,Unknown
limitNoExample value: 500
Behavior2/5

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

No annotations provided, so the description must carry the behavioral burden. It fails to disclose traits like data freshness, whether it's read-only, pagination, or what happens with no parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, but it is vague and poorly structured ('for given region or area and other filtering parameter'). Could be more precise and front-loaded with the action.

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?

No output schema, yet the description does not explain return format or structure. With 10 optional parameters and no required ones, lacks guidance on valid combinations or defaults.

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

Parameters2/5

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

Schema coverage is 100% but descriptions are minimal (e.g., examples only). The tool description adds no parameter info beyond the schema, missing meanings for codes like 'AM' or 'AL'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it provides 'US weather alert daily information' for a region/area, which identifies the resource but lacks a specific verb (e.g., 'retrieve', 'list'). It does not differentiate from siblings like current_weather or forecast_weather.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description only implies general usage for a given region/area, with no exclusions or prerequisites.

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