Skip to main content
Glama
MaxwellCalkin

N2YO Satellite Tracker MCP Server

get_recent_launches

Retrieve satellites launched within the past 30 days using N2YO Satellite Tracker data to monitor recent space activity.

Instructions

Get satellites launched in the last 30 days

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.ts:276-283 (registration)
    Tool registration entry defining the name, description, and input schema (no required parameters) for get_recent_launches.
    {
      name: "get_recent_launches",
      description: "Get satellites launched in the last 30 days",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Main handler function that invokes the N2YO client to retrieve recent launches and formats the result as a CallToolResult for the MCP protocol.
    private async getRecentLaunches(): Promise<CallToolResult> {
      const launches = await this.n2yoClient.getRecentLaunches();
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({ 
              timeRange: "Last 30 days",
              recentLaunches: launches, 
              count: launches.length,
              note: "Recently launched satellites with current position data"
            }, null, 2),
          },
        ],
      };
    }
  • Dispatch case in callTool method that routes the tool name to the specific handler.
    case "get_recent_launches":
      return await this.getRecentLaunches();
  • Supporting method in N2YO client that queries the API for satellites launched in the last 30 days.
    async getRecentLaunches(): Promise<RecentLaunch[]> {
      const now = new Date();
      const thirtyDaysAgo = new Date(now.getTime() - 30 * 24 * 60 * 60 * 1000);
      const startDate = thirtyDaysAgo.toISOString().split('T')[0];
      const endDate = now.toISOString().split('T')[0];
      
      const response = await this.makeRequest(`/launchDate/${startDate}/${endDate}`, {
        startDate,
        endDate,
      });
    
      return response.above || [];
    }
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 states what the tool does but lacks details on permissions, rate limits, response format, or error handling. For a tool with zero annotation coverage, this is a significant gap in transparency, though it doesn't contradict any annotations.

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 that efficiently conveys the tool's purpose without any redundant or unnecessary words. It is front-loaded with the core action and scope, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema) and lack of annotations, the description is adequate as a minimum viable explanation. It covers the basic purpose but lacks details on behavioral aspects like response format or error handling, which would be beneficial for completeness despite the low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description adds context by specifying the time frame ('last 30 days'), which is valuable semantic information not captured in the schema, justifying a score above the baseline of 3.

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') and resource ('satellites launched in the last 30 days'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from its siblings like 'get_satellites_by_category' or 'search_satellites_by_name', which might also retrieve satellite data but with different filters or scopes.

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 implies usage for recent satellite launches within a 30-day window, but it provides no explicit guidance on when to use this tool versus alternatives such as 'get_satellites_by_category' or 'query_satellites_natural'. There are no exclusions or prerequisites mentioned, leaving the agent to infer appropriate contexts.

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