Skip to main content
Glama
MaxwellCalkin

N2YO Satellite Tracker MCP Server

get_visual_passes

Predict visible satellite passes for a specific location by entering satellite NORAD ID and observer coordinates to plan observation sessions.

Instructions

Get upcoming visual 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)
minVisibilityNoMinimum visibility in seconds (max 300)

Implementation Reference

  • Main handler for the 'get_visual_passes' tool: validates input, calls N2YO client to retrieve visual passes, and returns a JSON-formatted response with the passes data.
    private async getVisualPasses(args: any): Promise<CallToolResult> {
      SatelliteValidator.validateVisualPassRequest(args);
    
      const passes = await this.n2yoClient.getVisualPasses(
        args.noradId,
        args.observerLat,
        args.observerLng,
        args.observerAlt || 0,
        args.days || 10,
        args.minVisibility || 300
      );
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({ passes, count: passes.length }, null, 2),
          },
        ],
      };
    }
  • src/server.ts:175-218 (registration)
    Tool registration in getTools() method, including name, description, and input schema definition for 'get_visual_passes'.
    {
      name: "get_visual_passes",
      description:
        "Get upcoming visual 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,
          },
          minVisibility: {
            type: "number",
            description: "Minimum visibility in seconds (max 300)",
            default: 300,
            maximum: 300,
          },
        },
        required: ["noradId", "observerLat", "observerLng"],
      },
    },
  • N2YOClient helper method that constructs and sends the API request for visual passes, returning the passes array.
    async getVisualPasses(
      noradId: string,
      observerLat: number,
      observerLng: number,
      observerAlt: number = 0,
      days: number = 10,
      minVisibility: number = 300
    ): Promise<VisualPass[]> {
      const response = await this.makeRequest(`/visualpasses/${noradId}/${observerLat}/${observerLng}/${observerAlt}/${days}/${minVisibility}`, {
        id: noradId,
        observer_lat: observerLat,
        observer_lng: observerLng,
        observer_alt: observerAlt,
        days,
        min_visibility: minVisibility,
      });
    
      return response.passes || [];
    }
  • TypeScript interface defining the structure of a VisualPass object returned by the tool.
    export interface VisualPass {
      startAz: number;
      startAzCompass: string;
      startEl: number;
      startUTC: number;
      maxAz: number;
      maxAzCompass: string;
      maxEl: number;
      maxUTC: number;
      endAz: number;
      endAzCompass: string;
      endEl: number;
      endUTC: number;
      mag: number;
      duration: number;
    }
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 but only states what the tool does without explaining how it behaves. It doesn't cover aspects like rate limits, authentication needs, error handling, or what 'visual passes' entail (e.g., visibility conditions, timeframes), leaving significant gaps in understanding the tool's operational traits.

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, front-loaded sentence that efficiently conveys the core functionality without unnecessary words. It uses clear terminology ('upcoming visual passes', 'satellite', 'observer location') and avoids redundancy, making it easy to parse while fully earning its place in the tool definition.

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 and the lack of annotations and output schema, the description is insufficiently complete. It doesn't explain what 'visual passes' are, the format of returned data, or any limitations beyond implied ones, leaving the agent with inadequate context to effectively use this tool in practice.

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 adds no parameter-specific information beyond what the input schema already provides, as schema description coverage is 100% with detailed descriptions for all parameters. This meets the baseline score of 3, as the schema adequately documents parameters like 'noradId' and 'observerLat', but the description doesn't enhance understanding with additional context or examples.

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 visual 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_radio_passes' or 'get_satellite_position', which reduces clarity in a server with multiple satellite-related tools.

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_radio_passes' for radio passes or 'get_satellite_position' for current positions. It lacks any mention of prerequisites, exclusions, or specific use cases, leaving the agent to infer usage from the tool name 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