Skip to main content
Glama
MaxwellCalkin

N2YO Satellite Tracker MCP Server

get_satellites_above

Find satellites currently visible from your location by entering latitude and longitude coordinates. Filter results by satellite category to identify specific types overhead.

Instructions

Get all satellites currently above an observer location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
observerLatYesObserver latitude in degrees
observerLngYesObserver longitude in degrees
observerAltNoObserver altitude in meters above sea level
searchRadiusNoSearch radius in degrees (max 90)
categoryFilterNoFilter results by satellite categoryall

Implementation Reference

  • src/server.ts:354-392 (registration)
    Tool registration in getTools() method, defining the name, description, and input schema for 'get_satellites_above'
    {
      name: "get_satellites_above",
      description: "Get all satellites currently above an observer location",
      inputSchema: {
        type: "object",
        properties: {
          observerLat: {
            type: "number",
            description: "Observer latitude in degrees",
            minimum: -90,
            maximum: 90,
          },
          observerLng: {
            type: "number",
            description: "Observer longitude in degrees",
            minimum: -180,
            maximum: 180,
          },
          observerAlt: {
            type: "number",
            description: "Observer altitude in meters above sea level",
            default: 0,
          },
          searchRadius: {
            type: "number",
            description: "Search radius in degrees (max 90)",
            default: 70,
            maximum: 90,
          },
          categoryFilter: {
            type: "string",
            enum: ["all", "military", "weather", "gps", "amateur"],
            default: "all",
            description: "Filter results by satellite category",
          },
        },
        required: ["observerLat", "observerLng"],
      },
    },
  • Primary handler function for executing the 'get_satellites_above' tool: validates arguments, maps category filter, calls N2YO client, and returns formatted JSON response.
    private async getSatellitesAbove(args: any): Promise<CallToolResult> {
      SatelliteValidator.validateAboveRequest(args);
    
      const categoryId =
        args.categoryFilter && args.categoryFilter !== "all"
          ? this.n2yoClient.getCategoryId(args.categoryFilter)
          : 0;
    
      const satellites = await this.n2yoClient.getSatellitesAbove(
        args.observerLat,
        args.observerLng,
        args.observerAlt || 0,
        args.searchRadius || 70,
        categoryId
      );
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              { satellites, count: satellites.length },
              null,
              2
            ),
          },
        ],
      };
    }
  • Core helper method in N2YOClient that performs the actual API request to retrieve satellites above the specified location and returns raw data.
    async getSatellitesAbove(
      observerLat: number,
      observerLng: number,
      observerAlt: number = 0,
      searchRadius: number = 70,
      categoryFilter: number = 0
    ): Promise<SatelliteAbove[]> {
      const response = await this.makeRequest(`/above/${observerLat}/${observerLng}/${observerAlt}/${searchRadius}/${categoryFilter}`, {
        observer_lat: observerLat,
        observer_lng: observerLng,
        observer_alt: observerAlt,
        search_radius: searchRadius,
        category_filter: categoryFilter,
      });
    
      return response.above || [];
    }
  • TypeScript interface defining the structure of satellite data returned by getSatellitesAbove.
    export interface SatelliteAbove {
      satid: number;
      satname: string;
      intDesignator: string;
      launchDate: string;
      satlat: number;
      satlng: number;
      satalt: number;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does without behavioral details. It doesn't disclose if this is a read-only operation, requires authentication, has rate limits, returns real-time vs. cached data, or what the output format looks like (e.g., list of satellites with properties).

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 with no wasted words, making it easy to parse and front-loaded with the core functionality. It efficiently communicates the essential action without unnecessary elaboration.

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 complexity of satellite tracking (5 parameters, no output schema, no annotations), the description is incomplete. It doesn't cover output details, error conditions, or behavioral traits like data freshness or API dependencies, leaving significant gaps for an AI agent to use the tool effectively.

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 description implies parameters for observer location but doesn't add meaning beyond the schema, which has 100% coverage with detailed descriptions for all 5 parameters. It doesn't explain relationships between parameters (e.g., how 'searchRadius' interacts with location) or provide usage examples, so it meets the baseline for high schema coverage.

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 'satellites currently above an observer location', making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_visual_passes' or 'get_radio_passes', which might have overlapping functionality for satellite observation.

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 like 'get_satellites_by_category' or 'query_satellites_natural'. It lacks context about prerequisites, such as needing an API key (implied by 'set_n2yo_api_key' sibling), or exclusions like time-based filtering.

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/MaxwellCalkin/N2YO-MCP'

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