Skip to main content
Glama
adarshem

MCP Weather Server

get-forecast

Fetch weather forecasts for any location using latitude and longitude coordinates via the MCP Weather Server, powered by the US National Weather Service API.

Instructions

Get weather forecast for a location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesLatitude of the location
longitudeYesLongitude of the location

Implementation Reference

  • Handler function that fetches weather grid points, retrieves forecast data from NWS API, formats periods with temperature, wind, and short forecast, and returns formatted text response.
    async ({ latitude, longitude }) => {
      // Get grid point data
      const pointsUrl = `${NWS_API_BASE}/points/${latitude.toFixed(
        4
      )},${longitude.toFixed(4)}`;
      const pointsData = await makeNWSRequest<PointsResponse>(pointsUrl);
    
      if (!pointsData) {
        return {
          content: [
            {
              type: 'text',
              text: `Failed to retrieve grid point data for coordinates: ${latitude}, ${longitude}. This location may not be supported by the NWS API (only US locations are supported).`
            }
          ]
        };
      }
    
      const forecastUrl = pointsData.properties?.forecast;
      if (!forecastUrl) {
        return {
          content: [
            {
              type: 'text',
              text: 'Failed to get forecast URL from grid point data'
            }
          ]
        };
      }
    
      // Get forecast data
      const forecastData = await makeNWSRequest<ForecastResponse>(forecastUrl);
      if (!forecastData) {
        return {
          content: [
            {
              type: 'text',
              text: 'Failed to retrieve forecast data'
            }
          ]
        };
      }
    
      const periods = forecastData.properties?.periods || [];
      if (periods.length === 0) {
        return {
          content: [
            {
              type: 'text',
              text: 'No forecast periods available'
            }
          ]
        };
      }
    
      // Format forecast periods
      const formattedForecast = periods.map((period: ForecastPeriod) =>
        [
          `${period.name || 'Unknown'}:`,
          `Temperature: ${period.temperature || 'Unknown'}°${
            period.temperatureUnit || 'F'
          }`,
          `Wind: ${period.windSpeed || 'Unknown'} ${period.windDirection || ''}`,
          `${period.shortForecast || 'No forecast available'}`,
          '---'
        ].join('\n')
      );
    
      const forecastText = `Forecast for ${latitude}, ${longitude}:\n\n${formattedForecast.join(
        '\n'
      )}`;
    
      return {
        content: [
          {
            type: 'text',
            text: forecastText
          }
        ]
      };
    }
  • Zod input schema validating latitude (-90 to 90) and longitude (-180 to 180) parameters.
    {
      latitude: z.number().min(-90).max(90).describe('Latitude of the location'),
      longitude: z
        .number()
        .min(-180)
        .max(180)
        .describe('Longitude of the location')
    },
  • src/index.ts:136-228 (registration)
    Full tool registration using server.tool, including name, description, input schema, and inline handler function.
    server.tool(
      'get-forecast',
      'Get weather forecast for a location',
      {
        latitude: z.number().min(-90).max(90).describe('Latitude of the location'),
        longitude: z
          .number()
          .min(-180)
          .max(180)
          .describe('Longitude of the location')
      },
      async ({ latitude, longitude }) => {
        // Get grid point data
        const pointsUrl = `${NWS_API_BASE}/points/${latitude.toFixed(
          4
        )},${longitude.toFixed(4)}`;
        const pointsData = await makeNWSRequest<PointsResponse>(pointsUrl);
    
        if (!pointsData) {
          return {
            content: [
              {
                type: 'text',
                text: `Failed to retrieve grid point data for coordinates: ${latitude}, ${longitude}. This location may not be supported by the NWS API (only US locations are supported).`
              }
            ]
          };
        }
    
        const forecastUrl = pointsData.properties?.forecast;
        if (!forecastUrl) {
          return {
            content: [
              {
                type: 'text',
                text: 'Failed to get forecast URL from grid point data'
              }
            ]
          };
        }
    
        // Get forecast data
        const forecastData = await makeNWSRequest<ForecastResponse>(forecastUrl);
        if (!forecastData) {
          return {
            content: [
              {
                type: 'text',
                text: 'Failed to retrieve forecast data'
              }
            ]
          };
        }
    
        const periods = forecastData.properties?.periods || [];
        if (periods.length === 0) {
          return {
            content: [
              {
                type: 'text',
                text: 'No forecast periods available'
              }
            ]
          };
        }
    
        // Format forecast periods
        const formattedForecast = periods.map((period: ForecastPeriod) =>
          [
            `${period.name || 'Unknown'}:`,
            `Temperature: ${period.temperature || 'Unknown'}°${
              period.temperatureUnit || 'F'
            }`,
            `Wind: ${period.windSpeed || 'Unknown'} ${period.windDirection || ''}`,
            `${period.shortForecast || 'No forecast available'}`,
            '---'
          ].join('\n')
        );
    
        const forecastText = `Forecast for ${latitude}, ${longitude}:\n\n${formattedForecast.join(
          '\n'
        )}`;
    
        return {
          content: [
            {
              type: 'text',
              text: forecastText
            }
          ]
        };
      }
    );
  • Helper function to make authenticated fetch requests to the National Weather Service (NWS) API, handling errors and returning typed JSON or null.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but fails to describe key behavioral traits such as whether it's a read-only operation, potential rate limits, authentication requirements, error handling, or the format of returned data. This leaves significant gaps for an agent to understand how to interact with it effectively.

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 directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized for a simple tool, with every part of the sentence contributing essential information. No waste or redundancy is present.

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 lack of annotations and output schema, the description is incomplete for a tool that likely returns complex weather data. It does not explain what the forecast includes (e.g., temperature, precipitation), timeframes, or data format. For a tool with no structured output documentation, the description should provide more context to help the agent understand the return values and usage implications.

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 input schema has 100% description coverage, with clear documentation for both parameters (latitude and longitude). The description does not add any additional meaning beyond what the schema provides, such as explaining coordinate systems or units. However, with high schema coverage, the baseline score of 3 is appropriate as the schema adequately handles parameter semantics.

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 tool's purpose with a specific verb ('Get') and resource ('weather forecast for a location'). It distinguishes from the sibling tool 'get-alerts' by focusing on forecasts rather than alerts, though the distinction could be more explicit. The description avoids tautology by not simply restating the name.

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?

The description provides no guidance on when to use this tool versus the sibling 'get-alerts' or any other alternatives. It lacks context about use cases, prerequisites, or exclusions. The agent must infer usage solely from the tool name and description without explicit direction.

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