Skip to main content
Glama
WeatherXM

WeatherXM Pro MCP Server

Official
by WeatherXM

get_historical_observations

Retrieve weather data for a specific station and date from the WeatherXM Pro MCP Server to analyze historical weather observations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate (YYYY-MM-DD) for historical observations
station_idYesThe unique identifier of the station

Implementation Reference

  • Handler function that fetches historical weather observations for a given station ID and date from the WeatherXM API, handles errors, and returns JSON-formatted response.
    async ({ station_id, date }) => {
      try {
        const response = await axiosInstance.get(`/stations/${station_id}/history`, {
          params: { date },
        });
        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 input schema defining required parameters: station_id (string) and date (string in YYYY-MM-DD format).
    {
      station_id: z.string().describe("The unique identifier of the station"),
      date: z.string().describe("Date (YYYY-MM-DD) for historical observations"),
    },
  • src/index.ts:135-159 (registration)
    Registration of the 'get_historical_observations' tool with the MCP server using server.tool(), including inline schema and handler.
    server.tool(
      "get_historical_observations",
      {
        station_id: z.string().describe("The unique identifier of the station"),
        date: z.string().describe("Date (YYYY-MM-DD) for historical observations"),
      },
      async ({ station_id, date }) => {
        try {
          const response = await axiosInstance.get(`/stations/${station_id}/history`, {
            params: { date },
          });
          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