Skip to main content
Glama
YunYouJun

Starter MCP Server

by YunYouJun

Weather forecast

get-forecast

Retrieve weather forecast data for specific geographic coordinates by providing latitude and longitude values.

Instructions

Get weather forecast for a location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesLatitude of the location
longitudeYesLongitude of the location

Implementation Reference

  • The handler function that implements the 'get-forecast' tool logic. It fetches the NWS grid points for given lat/lon, retrieves the forecast data, formats the forecast periods, and returns a 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 defining latitude and longitude parameters for the tool.
    inputSchema: z.object({
      latitude: z.number().min(-90).max(90).describe('Latitude of the location'),
      longitude: z
        .number()
        .min(-180)
        .max(180)
        .describe('Longitude of the location'),
    }),
  • The registerGetForecast function that calls server.registerTool to register the 'get-forecast' tool with its schema and handler.
    export function registerGetForecast() {
      server.registerTool(
        'get-forecast',
        {
          title: 'Weather forecast',
          description: 'Get weather forecast for a location',
          inputSchema: z.object({
            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,
              },
            ],
          }
        },
      )
    }
  • src/index.ts:10-10 (registration)
    The call to registerGetForecast() in the main index file, which triggers the tool registration.
    registerGetForecast()
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 the tool 'Get[s] weather forecast' but doesn't elaborate on what the forecast includes (e.g., temperature, precipitation), time range, data source, rate limits, error handling, or authentication needs. This leaves significant gaps in understanding the tool's behavior beyond the basic action.

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: 'Get weather forecast for a location.' It is front-loaded with the core purpose, has zero wasted words, and is appropriately sized for a simple tool. Every part of the sentence contributes directly to understanding the tool's function.

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's moderate complexity (weather forecasting with geographic parameters) and the absence of annotations and output schema, the description is incomplete. It doesn't explain what the forecast returns (e.g., data format, time periods), potential limitations, or how to interpret results. For a tool with no structured output information, more descriptive context is needed.

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 description coverage is 100%, with both parameters (latitude and longitude) fully documented in the input schema. The description doesn't add any parameter-specific details beyond what the schema provides, such as format examples or usage tips. However, since the schema covers all parameters adequately, the baseline score of 3 is appropriate.

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: 'Get weather forecast for a location' specifies the verb ('Get') and resource ('weather forecast') with the target ('location'). It distinguishes from the sibling tool 'get-alerts' by focusing on forecasts rather than alerts, though the distinction isn't explicitly stated. The purpose is specific and actionable.

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 alternatives. It doesn't mention the sibling tool 'get-alerts' or any other tools, nor does it specify prerequisites, constraints, or typical use cases. Without such context, the agent must infer usage based solely on the tool name and description.

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/YunYouJun/starter-mcp-server'

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