Skip to main content
Glama
MaxwellCalkin

N2YO Satellite Tracker MCP Server

set_n2yo_api_key

Configure your N2YO API key to enable satellite tracking functionality, including position queries, pass predictions, and TLE data access.

Instructions

Configure N2YO API key for satellite tracking

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyYesN2YO API key from your account

Implementation Reference

  • The primary handler function for the set_n2yo_api_key tool. It validates the provided API key and sets it on the N2YOClient instance, then returns a success response.
    private async setApiKey(apiKey: string): Promise<CallToolResult> {
      SatelliteValidator.validateApiKey(apiKey);
      this.n2yoClient.setApiKey(apiKey);
    
      return {
        content: [
          {
            type: "text",
            text: "Successfully configured N2YO API key",
          },
        ],
      };
    }
  • Runtime input validation for the API key parameter, enforcing type, length, and character set requirements.
    static validateApiKey(apiKey: string): void {
      if (!apiKey || typeof apiKey !== "string") {
        throw new ValidationError("API key is required and must be a string");
      }
    
      if (apiKey.length < 10 || apiKey.length > 100) {
        throw new ValidationError("API key must be between 10 and 100 characters");
      }
    
      if (!/^[a-zA-Z0-9-_]+$/.test(apiKey)) {
        throw new ValidationError("API key must contain only alphanumeric characters, hyphens, and underscores");
      }
    }
  • src/server.ts:20-33 (registration)
    Tool registration definition in the getTools() method, specifying name, description, and input schema.
    {
      name: "set_n2yo_api_key",
      description: "Configure N2YO API key for satellite tracking",
      inputSchema: {
        type: "object",
        properties: {
          apiKey: {
            type: "string",
            description: "N2YO API key from your account",
          },
        },
        required: ["apiKey"],
      },
    },
  • Helper method in N2YOClient that stores the API key in the client instance for use in subsequent API requests.
    setApiKey(apiKey: string): void {
      this.apiKey = apiKey;
    }
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. 'Configure' implies a write/mutation operation that likely persists settings, but the description doesn't specify whether this is required before using other tools, if it's reversible, what happens on failure, or if it affects all subsequent operations. Significant behavioral context is missing.

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 directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 configuration/mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain the relationship to sibling tools (which all appear to depend on this API key), what happens after configuration, error conditions, or persistence scope. The context signals suggest this is a critical setup tool, but the description doesn't reflect that importance.

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% (the single parameter 'apiKey' is fully described in the schema as 'N2YO API key from your account'). The description adds no additional parameter information beyond what the schema already provides, meeting the baseline expectation when schema coverage is high.

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 ('Configure') and the resource ('N2YO API key for satellite tracking'), making the purpose evident. However, it doesn't distinguish this tool from its siblings, which are all read-only satellite data retrieval tools, while this one appears to be a configuration/write operation.

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. Given that all sibling tools are read-only satellite data queries, this tool likely sets up authentication for those operations, but this relationship isn't explained. No prerequisites, timing, or exclusion criteria are 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