Skip to main content
Glama
adarshem

MCP Weather Server

get-alerts

Fetch real-time weather alerts for any US state by providing a two-letter state code using the MCP Weather Server.

Instructions

Get weather alerts for a state

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYesTwo-letter state code (e.g. CA, NY)

Implementation Reference

  • The main handler function for the 'get-alerts' tool. Fetches alerts from the National Weather Service API for a given state code, handles errors and empty results, formats the alerts using the formatAlert helper, and returns them as formatted text content.
    async ({ state }) => {
      const stateCode = state.toUpperCase();
      const alertsUrl = `${NWS_API_BASE}/alerts?area=${stateCode}`;
      const alertsData = await makeNWSRequest<AlertsResponse>(alertsUrl);
    
      if (!alertsData) {
        return {
          content: [
            {
              type: 'text',
              text: 'Failed to retrieve alerts data'
            }
          ]
        };
      }
    
      const features = alertsData.features || [];
      if (features.length === 0) {
        return {
          content: [
            {
              type: 'text',
              text: `No active alerts for ${stateCode}`
            }
          ]
        };
      }
    
      const formattedAlerts = features.map(formatAlert);
      const alertsText = `Active alerts for ${stateCode}:\n\n${formattedAlerts.join(
        '\n'
      )}`;
    
      return {
        content: [
          {
            type: 'text',
            text: alertsText
          }
        ]
      };
    }
  • Input schema for the 'get-alerts' tool, validating the 'state' parameter as a two-letter string using Zod.
    {
      state: z.string().length(2).describe('Two-letter state code (e.g. CA, NY)')
    },
  • src/index.ts:86-134 (registration)
    Registration of the 'get-alerts' tool on the MCP server, specifying name, description, input schema, and inline handler function.
    server.tool(
      'get-alerts',
      'Get weather alerts for a state',
      {
        state: z.string().length(2).describe('Two-letter state code (e.g. CA, NY)')
      },
      async ({ state }) => {
        const stateCode = state.toUpperCase();
        const alertsUrl = `${NWS_API_BASE}/alerts?area=${stateCode}`;
        const alertsData = await makeNWSRequest<AlertsResponse>(alertsUrl);
    
        if (!alertsData) {
          return {
            content: [
              {
                type: 'text',
                text: 'Failed to retrieve alerts data'
              }
            ]
          };
        }
    
        const features = alertsData.features || [];
        if (features.length === 0) {
          return {
            content: [
              {
                type: 'text',
                text: `No active alerts for ${stateCode}`
              }
            ]
          };
        }
    
        const formattedAlerts = features.map(formatAlert);
        const alertsText = `Active alerts for ${stateCode}:\n\n${formattedAlerts.join(
          '\n'
        )}`;
    
        return {
          content: [
            {
              type: 'text',
              text: alertsText
            }
          ]
        };
      }
    );
  • Helper function to format a single weather alert feature into a multi-line string, used within the get-alerts handler.
    function formatAlert(feature: AlertFeature): string {
      const props = feature.properties;
      return [
        `Event: ${props.event || 'Unknown'}`,
        `Area: ${props.areaDesc || 'Unknown'}`,
        `Severity: ${props.severity || 'Unknown'}`,
        `Status: ${props.status || 'Unknown'}`,
        `Headline: ${props.headline || 'No headline'}`,
        '---'
      ].join('\n');
    }
  • Generic helper function for making authenticated requests to the National Weather Service API, used by the get-alerts handler.
    async function makeNWSRequest<T>(url: string): Promise<T | null> {
      const headers = {
        'User-Agent': USER_AGENT,
        Accept: 'application/geo+json'
      };
    
      try {
        const response = await fetch(url, { headers });
        if (!response.ok) {
          throw new Error(`HTTP error! status: ${response.status}`);
        }
        return (await response.json()) as T;
      } catch (error) {
        console.error('Error making NWS request:', error);
        return null;
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't describe how it behaves - no information about response format, error conditions, rate limits, authentication requirements, or whether it's a read-only operation.

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, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a simple tool with one parameter.

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

Completeness3/5

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

For a simple read operation with one well-documented parameter and no output schema, the description provides basic functionality but lacks important context about response format and behavioral characteristics that would help an agent use it effectively.

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?

The schema has 100% description coverage, with the parameter 'state' clearly documented as a two-letter code. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('Get') and resource ('weather alerts for a state'), making the purpose immediately understandable. It doesn't explicitly distinguish from the sibling tool 'get-forecast', but the focus on alerts vs. forecast provides implicit differentiation.

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 explicit guidance is provided about when to use this tool versus the sibling 'get-forecast' tool. The description implies it's for weather alerts specifically, but there's no mention of alternatives, prerequisites, or exclusions.

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

Related 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/adarshem/mcp-server-learn'

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