Skip to main content
Glama
MaxwellCalkin

N2YO Satellite Tracker MCP Server

get_satellites_by_category

Retrieve satellites filtered by specific categories like military, weather, GPS, or Starlink to track and analyze orbital data.

Instructions

Get satellites by predefined categories (military, weather, GPS, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesSatellite category to retrieve
countryNoFilter by country or organization (e.g., 'usa', 'china', 'russia')

Implementation Reference

  • The main handler function for the 'get_satellites_by_category' tool. It validates inputs, retrieves category information from N2YO client, and returns a JSON response with category details and a link to the N2YO website for browsing satellites.
    private async getSatellitesByCategory(
      category: string,
      country?: string
    ): Promise<CallToolResult> {
      SatelliteValidator.validateCategory(category);
      SatelliteValidator.validateCountry(country);
    
      const categories = this.n2yoClient.getAvailableCategories();
      const categoryInfo = categories.find((cat) => cat.name === category);
    
      const result = {
        category: categoryInfo,
        country_filter: country,
        note: "Use the N2YO website to browse satellites by category and country, then use get_satellite_tle with specific NORAD IDs",
        website_url: `https://www.n2yo.com/satellites/?c=${
          categoryInfo?.id || 0
        }`,
      };
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • src/server.ts:104-135 (registration)
    Tool registration in the getTools() method, defining the tool name, description, and input schema with category enum and optional country filter.
    {
      name: "get_satellites_by_category",
      description:
        "Get satellites by predefined categories (military, weather, GPS, etc.)",
      inputSchema: {
        type: "object",
        properties: {
          category: {
            type: "string",
            enum: [
              "military",
              "weather",
              "gps",
              "navigation",
              "amateur",
              "geostationary",
              "noaa",
              "starlink",
              "space-stations",
              "earth-resources",
            ],
            description: "Satellite category to retrieve",
          },
          country: {
            type: "string",
            description:
              "Filter by country or organization (e.g., 'usa', 'china', 'russia')",
          },
        },
        required: ["category"],
      },
    },
  • Input schema definition for the tool, specifying object type with required 'category' enum and optional 'country' string.
    inputSchema: {
      type: "object",
      properties: {
        category: {
          type: "string",
          enum: [
            "military",
            "weather",
            "gps",
            "navigation",
            "amateur",
            "geostationary",
            "noaa",
            "starlink",
            "space-stations",
            "earth-resources",
          ],
          description: "Satellite category to retrieve",
        },
        country: {
          type: "string",
          description:
            "Filter by country or organization (e.g., 'usa', 'china', 'russia')",
        },
      },
      required: ["category"],
    },
  • src/server.ts:441-445 (registration)
    Dispatcher case in callTool() method that routes the tool call to the handler function.
    case "get_satellites_by_category":
      return await this.getSatellitesByCategory(
        args.category,
        args.country
      );
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 only states the basic action ('Get satellites') without revealing any behavioral traits such as whether this is a read-only operation, potential rate limits, authentication requirements, error conditions, or what the output looks like. For a tool with no annotations, 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 that front-loads the core purpose without unnecessary words. It uses parentheses to provide helpful examples without cluttering the main statement. Every element earns its place, 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 complexity (2 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain what the tool returns (e.g., list of satellites, details, or just counts), any limitations (e.g., pagination, data freshness), or how it interacts with other tools. For a retrieval tool with multiple siblings, more context is needed to guide effective use.

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%, with both parameters well-documented in the schema (including enum values for 'category' and examples for 'country'). The description adds minimal value beyond the schema by mentioning 'predefined categories' and listing examples like 'military, weather, GPS, etc.', which partially overlaps with the enum. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 resource 'satellites' with the specific filtering mechanism 'by predefined categories', which is more specific than just the tool name. It distinguishes from siblings like 'search_satellites_by_name' (which filters by name) and 'get_satellites_above' (which filters by location), though it doesn't explicitly mention these distinctions. The purpose is clear but could be more differentiated.

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 sibling tools like 'query_satellites_natural' or 'search_satellites_by_name', nor does it specify scenarios where category-based retrieval is preferred over other filtering methods. There's no information about prerequisites, limitations, or typical use cases.

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