Skip to main content
Glama
WeatherXM

WeatherXM Pro MCP Server

Official
by WeatherXM

get_forecast_for_cell

Retrieve weather forecast data for a specific H3 cell using the WeatherXM Pro MCP Server. Specify date range and forecast type (daily or hourly) for accurate weather predictions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forecast_cell_indexYesThe H3 index of the cell to get forecast for
forecast_fromYesThe first day for which to get forecast data (YYYY-MM-DD)
forecast_includeYesTypes of forecast to include
forecast_toYesThe last day for which to get forecast data (YYYY-MM-DD)

Implementation Reference

  • The asynchronous handler function that executes the tool logic: calls the WeatherXM API to fetch forecast data for a given H3 cell index and date range, returns JSON stringified response or handles errors.
    async ({ forecast_cell_index, forecast_from, forecast_to, forecast_include }) => {
      try {
        const response = await axiosInstance.get(`/cells/${forecast_cell_index}/forecast`, {
          params: {
            from: forecast_from,
            to: forecast_to,
            include: forecast_include,
          },
        });
        return {
          content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error: any) {
        if (axios.isAxiosError(error)) {
          return {
            content: [{ type: "text", text: `WeatherXM API error: ${error.response?.data.message ?? error.message}` }],
            isError: true,
          };
        }
        throw error;
      }
    }
  • Zod schema defining the input parameters for the tool: forecast_cell_index (string), forecast_from (string, YYYY-MM-DD), forecast_to (string, YYYY-MM-DD), forecast_include (enum: 'daily' or 'hourly').
    {
      forecast_cell_index: z.string().describe("The H3 index of the cell to get forecast for"),
      forecast_from: z.string().describe("The first day for which to get forecast data (YYYY-MM-DD)"),
      forecast_to: z.string().describe("The last day for which to get forecast data (YYYY-MM-DD)"),
      forecast_include: z.enum(['daily', 'hourly']).describe('Types of forecast to include'),
    },
  • src/index.ts:212-242 (registration)
    The server.tool() call that registers the 'get_forecast_for_cell' tool with its schema and inline handler function.
    server.tool(
      "get_forecast_for_cell",
      {
        forecast_cell_index: z.string().describe("The H3 index of the cell to get forecast for"),
        forecast_from: z.string().describe("The first day for which to get forecast data (YYYY-MM-DD)"),
        forecast_to: z.string().describe("The last day for which to get forecast data (YYYY-MM-DD)"),
        forecast_include: z.enum(['daily', 'hourly']).describe('Types of forecast to include'),
      },
      async ({ forecast_cell_index, forecast_from, forecast_to, forecast_include }) => {
        try {
          const response = await axiosInstance.get(`/cells/${forecast_cell_index}/forecast`, {
            params: {
              from: forecast_from,
              to: forecast_to,
              include: forecast_include,
            },
          });
          return {
            content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
          };
        } catch (error: any) {
          if (axios.isAxiosError(error)) {
            return {
              content: [{ type: "text", text: `WeatherXM API error: ${error.response?.data.message ?? error.message}` }],
              isError: true,
            };
          }
          throw error;
        }
      }
    );
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no 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

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/WeatherXM/weatherxm-pro-mcp'

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