Skip to main content
Glama
MaxwellCalkin

N2YO Satellite Tracker MCP Server

search_satellites_by_name

Find satellites by entering their name or international designator to access tracking data and orbital information.

Instructions

Search for satellites by name or international designator

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch term (satellite name or international designator)

Implementation Reference

  • The primary handler function for the 'search_satellites_by_name' tool. It validates the query input, delegates to the N2YOClient for search results, and returns a formatted CallToolResult.
    private async searchSatellitesByName(query: string): Promise<CallToolResult> {
      if (!query || query.trim().length === 0) {
        return {
          content: [
            {
              type: "text",
              text: "Search query cannot be empty",
            },
          ],
          isError: true,
        };
      }
    
      const results = this.n2yoClient.searchSatellitesByName(query.trim());
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({ 
              query: query.trim(),
              satellites: results, 
              count: results.length,
              note: "Use the NORAD ID (satid) to get more detailed information about specific satellites"
            }, null, 2),
          },
        ],
      };
    }
  • src/server.ts:262-275 (registration)
    Registration of the tool in the getTools() method, including name, description, and input schema definition.
    {
      name: "search_satellites_by_name",
      description: "Search for satellites by name or international designator",
      inputSchema: {
        type: "object",
        properties: {
          query: {
            type: "string",
            description: "Search term (satellite name or international designator)",
          },
        },
        required: ["query"],
      },
    },
  • Input schema defining the expected arguments for the tool (query string).
      inputSchema: {
        type: "object",
        properties: {
          query: {
            type: "string",
            description: "Search term (satellite name or international designator)",
          },
        },
        required: ["query"],
      },
    },
  • Helper method in N2YOClient class that implements the satellite search logic using a mock database filtered by name or designator.
    searchSatellitesByName(query: string): SatelliteSearchResult[] {
      // Mock search - in real implementation this would query N2YO or use a satellite database
      const mockSatellites = [
        { satid: 25544, satname: "ISS (ZARYA)", intDesignator: "1998-067A", launchDate: "1998-11-20" },
        { satid: 20580, satname: "HST", intDesignator: "1990-037B", launchDate: "1990-04-24" },
        { satid: 43013, satname: "STARLINK-1007", intDesignator: "2017-073A", launchDate: "2017-12-23" },
        { satid: 43014, satname: "STARLINK-1002", intDesignator: "2017-073B", launchDate: "2017-12-23" },
        { satid: 28654, satname: "NOAA 18", intDesignator: "2005-018A", launchDate: "2005-05-20" },
        { satid: 32786, satname: "AQUA", intDesignator: "2002-022A", launchDate: "2002-05-04" },
        { satid: 41866, satname: "GEOSAT FOLLOW-ON 2", intDesignator: "2016-064A", launchDate: "2016-08-19" },
      ];
    
      const searchTerm = query.toLowerCase();
      return mockSatellites.filter(sat => 
        sat.satname.toLowerCase().includes(searchTerm) ||
        sat.intDesignator.toLowerCase().includes(searchTerm)
      );
    }
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 tool is for searching, which implies a read-only operation, but doesn't specify aspects like whether it requires authentication, has rate limits, returns paginated results, or what the output format might be. For a tool with zero annotation coverage, this is a significant gap in transparency.

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: 'Search for satellites by name or international designator.' It is front-loaded with the core purpose, has no redundant words, and every part contributes directly to understanding the tool's function, 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.

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't address behavioral traits like authentication needs or result format, and while the parameter is covered by the schema, the overall context for a search tool with potential complexities (e.g., handling multiple matches, error cases) is underspecified. This makes it inadequate for full agent understanding.

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 input schema has 100% description coverage, with the 'query' parameter fully documented as 'Search term (satellite name or international designator).' The description adds no additional semantic details beyond this, such as examples or formatting tips. According to the rules, with high schema coverage, the baseline is 3, which is appropriate here.

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: 'Search for satellites by name or international designator.' It specifies both the verb ('Search') and the resource ('satellites'), making the function immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'query_satellites_natural' or 'query_satellites_with_tle,' which might also involve satellite queries, so it doesn't reach the highest score.

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 any prerequisites, exclusions, or compare it to siblings like 'query_satellites_natural' or 'get_satellites_by_category.' This lack of context leaves the agent to infer usage based on the tool name alone, which is insufficient for optimal selection.

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