Skip to main content
Glama
MaxwellCalkin

N2YO Satellite Tracker MCP Server

get_satellite_position

Calculate current satellite positions relative to observer coordinates using NORAD ID, latitude, and longitude for real-time tracking.

Instructions

Get current position of a satellite relative to 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
secondsNoNumber of seconds in the future for prediction (max 300)

Implementation Reference

  • The handler function that validates the input arguments and retrieves the satellite position data from the N2YOClient, returning the positions as a JSON-formatted result.
    private async getSatellitePosition(args: any): Promise<CallToolResult> {
      SatelliteValidator.validatePositionRequest(args);
    
      const positions = await this.n2yoClient.getPositions(
        args.noradId,
        args.observerLat,
        args.observerLng,
        args.observerAlt || 0,
        args.seconds || 0
      );
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({ positions, count: positions.length }, null, 2),
          },
        ],
      };
    }
  • The input schema defining the parameters for the tool, including noradId, observer location (lat, lng, alt), and optional seconds for prediction.
    {
      name: "get_satellite_position",
      description:
        "Get current position of a satellite relative to 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,
          },
          seconds: {
            type: "number",
            description:
              "Number of seconds in the future for prediction (max 300)",
            default: 0,
            maximum: 300,
          },
        },
        required: ["noradId", "observerLat", "observerLng"],
      },
    },
  • src/server.ts:447-448 (registration)
    The switch case in callTool method that routes calls to the getSatellitePosition handler.
    case "get_satellite_position":
      return await this.getSatellitePosition(args);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'current position' and 'relative to an observer location', but doesn't disclose behavioral traits like whether this requires API keys (sibling 'set_n2yo_api_key' suggests possible authentication), rate limits, error conditions, return format, or whether it's a real-time calculation versus cached data. The description is minimal and lacks operational context.

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 immediately states the tool's core function. There's no wasted language, repetition, or unnecessary elaboration. It's appropriately sized for a straightforward calculation tool.

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?

For a tool with 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the position output includes (coordinates, elevation, azimuth), accuracy considerations, time sensitivity, or dependencies. With rich sibling tools and no structured metadata, the description should provide more operational context to be complete.

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%, so the schema fully documents all 5 parameters. The description adds no parameter-specific information beyond implying the tool uses 'observer location' (which maps to observerLat, observerLng, observerAlt) and 'satellite' (noradId). It doesn't explain relationships between parameters or provide additional context beyond what's in the schema.

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 tool's purpose as 'Get current position of a satellite relative to an observer location', which specifies the action (get position), resource (satellite), and relationship (relative to observer). It distinguishes from siblings like 'get_satellite_trajectory' (trajectory vs position) and 'get_visual_passes' (passes vs position), though it doesn't explicitly name alternatives.

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. With siblings like 'get_satellites_above' (multiple satellites) and 'get_satellite_tle' (TLE data), there's no indication of when this specific position calculation is preferred. The description only states what it does, not when it's appropriate.

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