Skip to main content
Glama
hafizrahman

Weather & WordPress MCP Server

by hafizrahman

get-forecast

Retrieve weather forecast data for specific coordinates using latitude and longitude inputs to support planning and decision-making.

Instructions

Get weather forecast for a location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesLatitude of the location
longitudeYesLongitude of the location

Implementation Reference

  • The async handler function for the 'get-forecast' tool. It fetches the weather points URL from NWS API using lat/long, then retrieves and formats the forecast periods including temperature, wind, and short forecast.
    async ({ latitude, longitude }) => {
        const pointsUrl = `${NWS_API_BASE}/points/${latitude.toFixed(4)},${longitude.toFixed(4)}`;
        const pointsData = await fetchJson<PointsResponse>(pointsUrl, {
            Accept: "application/geo+json",
        });
    
        if (!pointsData || !pointsData.properties?.forecast) {
            return {
                content: [
                    {
                        type: "text",
                        text: `Failed to get forecast data for coordinates: ${latitude}, ${longitude}`,
                    },
                ],
            };
        }
    
        const forecastData = await fetchJson<ForecastResponse>(pointsData.properties.forecast);
        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" }],
            };
        }
    
        const formattedForecast = periods.map((period) =>
            [
                `${period.name || "Unknown"}:`,
                `Temperature: ${period.temperature || "Unknown"}°${period.temperatureUnit || "F"}`,
                `Wind: ${period.windSpeed || "Unknown"} ${period.windDirection || ""}`,
                `${period.shortForecast || "No forecast available"}`,
                "---",
            ].join("\n")
        );
    
        return {
            content: [{ type: "text", text: `Forecast for ${latitude}, ${longitude}:\n\n${formattedForecast.join("\n")}` }],
        };
    }
  • Input schema defined with Zod for latitude and longitude 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:112-164 (registration)
    Registration of the 'get-forecast' tool on the MCP server, specifying name, description, input schema, and 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 }) => {
            const pointsUrl = `${NWS_API_BASE}/points/${latitude.toFixed(4)},${longitude.toFixed(4)}`;
            const pointsData = await fetchJson<PointsResponse>(pointsUrl, {
                Accept: "application/geo+json",
            });
    
            if (!pointsData || !pointsData.properties?.forecast) {
                return {
                    content: [
                        {
                            type: "text",
                            text: `Failed to get forecast data for coordinates: ${latitude}, ${longitude}`,
                        },
                    ],
                };
            }
    
            const forecastData = await fetchJson<ForecastResponse>(pointsData.properties.forecast);
            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" }],
                };
            }
    
            const formattedForecast = periods.map((period) =>
                [
                    `${period.name || "Unknown"}:`,
                    `Temperature: ${period.temperature || "Unknown"}°${period.temperatureUnit || "F"}`,
                    `Wind: ${period.windSpeed || "Unknown"} ${period.windDirection || ""}`,
                    `${period.shortForecast || "No forecast available"}`,
                    "---",
                ].join("\n")
            );
    
            return {
                content: [{ type: "text", text: `Forecast for ${latitude}, ${longitude}:\n\n${formattedForecast.join("\n")}` }],
            };
        }
    );
  • TypeScript interfaces for NWS API responses: ForecastPeriod, PointsResponse, ForecastResponse (AlertsResponse is for another tool but in block). Used in get-forecast.
    interface ForecastPeriod {
        name?: string;
        temperature?: number;
        temperatureUnit?: string;
        windSpeed?: string;
        windDirection?: string;
        shortForecast?: string;
    }
    
    interface AlertsResponse {
        features: AlertFeature[];
    }
    
    interface PointsResponse {
        properties: {
            forecast?: string;
        };
    }
    
    interface ForecastResponse {
        properties: {
            periods: ForecastPeriod[];
        };
    }
  • Shared fetchJson utility function used to make API requests in the get-forecast handler.
    async function fetchJson<T>(url: string, headers: Record<string, string> = {}): Promise<T | null> {
        try {
            const response = await fetch(url, { headers: { "User-Agent": USER_AGENT, ...headers } });
            if (!response.ok) throw new Error(`HTTP error ${response.status}`);
            return (await response.json()) as T;
        } catch (err) {
            console.error("Fetch error:", err);
            return null;
        }
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe any behavioral traits such as whether this is a read-only operation, if it requires authentication, rate limits, or what the response format might be. This is inadequate for a tool with zero annotation coverage.

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 that efficiently conveys the core purpose without any unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 that there are no annotations and no output schema, the description is incomplete. It doesn't provide enough context about behavioral aspects, response format, or how this tool differs from its sibling. For a tool with this level of complexity and lack of structured data, the description should do more to compensate.

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) well-documented in the schema. The description doesn't add any meaningful parameter semantics beyond what's already in the schema, so it meets the baseline score of 3.

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 verb ('Get') and resource ('weather forecast for a location'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'get-alerts', which likely provides different weather-related information, so it doesn't achieve the highest score.

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 'get-alerts' or explain the difference between getting a forecast versus alerts, leaving the agent without context for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.