Skip to main content
Glama
MaxwellCalkin

N2YO Satellite Tracker MCP Server

get_radio_passes

Find upcoming satellite radio communication windows for your location by entering satellite ID and coordinates to plan observation sessions.

Instructions

Get upcoming radio communication passes of a satellite for an observer location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noradIdYesNORAD catalog number of the satellite
observerLatYesObserver latitude in degrees
observerLngYesObserver longitude in degrees
observerAltNoObserver altitude in meters above sea level
daysNoNumber of days to look ahead (max 10)
minElevationNoMinimum elevation in degrees (max 90)

Implementation Reference

  • src/server.ts:219-261 (registration)
    Tool registration including name, description, and input schema definition.
    {
      name: "get_radio_passes",
      description: "Get upcoming radio communication passes of a satellite for an observer location",
      inputSchema: {
        type: "object",
        properties: {
          noradId: {
            type: "string",
            description: "NORAD catalog number of the satellite",
          },
          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,
          },
          days: {
            type: "number",
            description: "Number of days to look ahead (max 10)",
            default: 10,
            maximum: 10,
          },
          minElevation: {
            type: "number",
            description: "Minimum elevation in degrees (max 90)",
            default: 10,
            maximum: 90,
          },
        },
        required: ["noradId", "observerLat", "observerLng"],
      },
    },
  • Primary MCP tool handler: validates args, fetches radio passes from client, formats and returns CallToolResult.
    private async getRadioPasses(args: any): Promise<CallToolResult> {
      SatelliteValidator.validateVisualPassRequest(args); // Same validation as visual passes
      
      const passes = await this.n2yoClient.getRadioPasses(
        args.noradId,
        args.observerLat,
        args.observerLng,
        args.observerAlt || 0,
        args.days || 10,
        args.minElevation || 10
      );
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({ 
              satellite: { noradId: args.noradId },
              observer: {
                latitude: args.observerLat,
                longitude: args.observerLng,
                altitude: args.observerAlt || 0,
              },
              radioPasses: passes, 
              count: passes.length,
              note: "Radio passes optimized for communication windows with elevation and timing data"
            }, null, 2),
          },
        ],
      };
    }
  • Core N2YO client method implementing the radio passes API call (mocked response).
    async getRadioPasses(
      noradId: string,
      observerLat: number,
      observerLng: number,
      observerAlt: number = 0,
      days: number = 10,
      minElevation: number = 10
    ): Promise<RadioPass[]> {
      const response = await this.makeRequest(`/radiopasses/${noradId}/${observerLat}/${observerLng}/${observerAlt}/${days}/${minElevation}`, {
        id: noradId,
        observer_lat: observerLat,
        observer_lng: observerLng,
        observer_alt: observerAlt,
        days,
        min_elevation: minElevation,
      });
    
      return response.passes || [];
    }
  • TypeScript interface defining the structure of radio pass data.
    export interface RadioPass {
      startAz: number;
      startAzCompass: string;
      startEl: number;
      startUTC: number;
      maxAz: number;
      maxAzCompass: string;
      maxEl: number;
      maxUTC: number;
      endAz: number;
      endAzCompass: string;
      endEl: number;
      endUTC: number;
    }
  • src/server.ts:456-457 (registration)
    Dispatch registration in callTool switch statement.
    case "get_radio_passes":
      return await this.getRadioPasses(args);
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 mentions 'upcoming' passes but doesn't specify timeframes, data freshness, rate limits, authentication needs, or error conditions. For a tool that likely queries external data with parameters like 'days' and 'minElevation', this leaves significant behavioral aspects undocumented.

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, efficient sentence that front-loads the core purpose without unnecessary words. Every element ('Get upcoming radio communication passes of a satellite for an observer location') directly contributes to understanding the tool's function, with zero wasted content.

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 pass calculations, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what constitutes a 'radio communication pass' versus other types, what data is returned (e.g., pass times, durations, elevations), or how results might be limited (e.g., by the 'days' parameter). This leaves the agent with inadequate context for effective use.

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?

Schema description coverage is 100%, providing clear documentation for all 6 parameters. The description adds no additional parameter semantics beyond what's in the schema, such as explaining relationships between parameters (e.g., how observer coordinates affect pass calculations) or typical usage patterns. This 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 action ('Get upcoming radio communication passes') and the resource ('of a satellite for an observer location'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_visual_passes' or 'get_satellites_above', which likely serve different observational purposes.

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 sibling tools like 'get_visual_passes' (which might be for optical observations) or 'get_satellites_above' (which might list satellites without pass details), leaving the agent to guess based on tool names alone.

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