Skip to main content
Glama
MaxwellCalkin

N2YO Satellite Tracker MCP Server

get_satellite_tle

Retrieve Two-Line Element (TLE) data for satellite tracking using NORAD ID to obtain orbital parameters for position calculations.

Instructions

Get Two-Line Element (TLE) data for a satellite by NORAD ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noradIdYesNORAD catalog number

Implementation Reference

  • Core handler function for the 'get_satellite_tle' tool. Validates NORAD ID, fetches TLE data via N2YO client, and returns formatted JSON response.
    private async getSatelliteTle(noradId: string): Promise<CallToolResult> {
      SatelliteValidator.validateNoradId(noradId);
    
      const tleData = await this.n2yoClient.getTle(noradId);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(tleData, null, 2),
          },
        ],
      };
    }
  • src/server.ts:89-103 (registration)
    Tool registration in getTools() method, defining name, description, and input schema for 'get_satellite_tle'.
    {
      name: "get_satellite_tle",
      description:
        "Get Two-Line Element (TLE) data for a satellite by NORAD ID",
      inputSchema: {
        type: "object",
        properties: {
          noradId: {
            type: "string",
            description: "NORAD catalog number",
          },
        },
        required: ["noradId"],
      },
    },
  • Input schema definition for the tool, specifying noradId as required string parameter.
    inputSchema: {
      type: "object",
      properties: {
        noradId: {
          type: "string",
          description: "NORAD catalog number",
        },
      },
      required: ["noradId"],
    },
  • Dispatch case in callTool method that routes 'get_satellite_tle' calls to the specific handler.
    case "get_satellite_tle":
      return await this.getSatelliteTle(args.noradId);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action is to 'Get' data, implying a read-only operation, but doesn't specify aspects like data freshness, rate limits, authentication needs, error handling, or what the return format looks like (e.g., raw TLE strings or structured data). This leaves significant gaps for an agent to understand how the tool behaves beyond its basic function.

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 key information ('Get Two-Line Element (TLE) data for a satellite by NORAD ID') with zero wasted words. It's appropriately sized for a simple tool with one parameter, making it easy to parse and understand quickly.

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 tool's moderate complexity (retrieving specific satellite data) and the lack of annotations and output schema, the description is incomplete. It doesn't explain what TLE data entails, the format of the return value, potential errors, or how it fits among sibling tools. This leaves the agent with insufficient context to use the tool effectively beyond the basic parameter input.

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 minimal meaning beyond the input schema, which has 100% coverage and fully documents the 'noradId' parameter as the 'NORAD catalog number'. The description restates this by mentioning 'by NORAD ID' but doesn't provide additional context like valid ID ranges, examples, or how to obtain the ID, so it meets the baseline for high schema coverage without compensating with extra insights.

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 the resource 'Two-Line Element (TLE) data for a satellite by NORAD ID', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_satellite_position' or 'get_satellite_trajectory', which might also involve satellite data retrieval but for different types of information.

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 multiple sibling tools related to satellites (e.g., 'get_satellite_position', 'get_satellite_trajectory', 'query_satellites_with_tle'), there is no indication of scenarios where TLE data is preferred over other satellite information, nor any prerequisites or exclusions mentioned.

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