Skip to main content
Glama
WeatherXM

WeatherXM Pro MCP Server

Official
by WeatherXM

get_stations_near

Find nearby weather stations by specifying latitude, longitude, and radius using the WeatherXM Pro MCP Server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude of the center of the area
lonYesLongitude of the center of the area
radiusYesRadius in meters for which stations are queried

Implementation Reference

  • The handler function that executes the logic for the get_stations_near tool by querying the WeatherXM Pro API endpoint '/stations/near' with lat, lon, radius parameters and returning the JSON data or error.
      async ({ lat, lon, radius }) => {
        try {
          const response = await axiosInstance.get('/stations/near', {
            params: { lat, lon, radius },
          });
          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 parameters lat (number), lon (number), radius (number) for the get_stations_near tool.
    {
      lat: z.number().describe("Latitude of the center of the area"),
      lon: z.number().describe("Longitude of the center of the area"),
      radius: z.number().describe("Radius in meters for which stations are queried"),
    },
  • src/index.ts:32-57 (registration)
    The registration of the get_stations_near tool via McpServer.tool() call, including inline schema and handler function.
    server.tool(
      "get_stations_near",
      {
        lat: z.number().describe("Latitude of the center of the area"),
        lon: z.number().describe("Longitude of the center of the area"),
        radius: z.number().describe("Radius in meters for which stations are queried"),
      },
      async ({ lat, lon, radius }) => {
        try {
          const response = await axiosInstance.get('/stations/near', {
            params: { lat, lon, radius },
          });
          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