N2YO Satellite Tracker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| set_n2yo_api_keyC | Configure N2YO API key for satellite tracking |
| query_satellites_naturalA | Answer natural language questions about satellites like 'What satellites will be over France at 6:00 tonight?' |
| query_satellites_with_tleC | Find satellites by natural language query and return structured data with Name and TLE |
| get_satellite_tleC | Get Two-Line Element (TLE) data for a satellite by NORAD ID |
| get_satellites_by_categoryC | Get satellites by predefined categories (military, weather, GPS, etc.) |
| get_satellite_positionC | Get current position of a satellite relative to an observer location |
| get_visual_passesC | Get upcoming visual passes of a satellite for an observer location |
| get_radio_passesC | Get upcoming radio communication passes of a satellite for an observer location |
| search_satellites_by_nameC | Search for satellites by name or international designator |
| get_recent_launchesB | Get satellites launched in the last 30 days |
| get_space_debrisC | Get space debris currently above an observer location |
| get_satellite_trajectoryC | Get satellite trajectory over time period for visualization |
| get_satellites_aboveC | Get all satellites currently above an observer location |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| N2YO API Status | Current N2YO API configuration and usage status |
| Satellite Categories | Available satellite categories for searching |
| Countries and Organizations | Available countries and organizations for satellite filtering |
| API Transaction Limits | Information about N2YO API transaction limits and usage |
TDQS
Scored across 13 tools
Most tools have distinct purposes, such as get_satellite_position for current location and get_visual_passes for future passes, but some overlap exists between get_satellites_above and get_space_debris, which both retrieve objects above a location, potentially causing confusion. The query_satellites_natural and query_satellites_with_tle also serve similar natural language query functions with minor differences in output.
All tool names follow a consistent snake_case pattern with clear verb_noun structures, such as get_satellite_position and search_satellites_by_name. The naming is predictable and uniform across all 13 tools, making them easy to distinguish and use in a cohesive manner.
With 13 tools, the server is well-scoped for satellite tracking, covering key operations like position retrieval, pass predictions, searches, and API configuration. Each tool serves a specific function without redundancy, making the count appropriate for the domain's complexity and user needs.
The tool set provides comprehensive coverage for satellite tracking, including position, passes, searches, and data retrieval, with minor gaps such as the lack of update or delete operations for satellite data, which may be inherent to the read-only nature of the API. Core workflows are well-supported, allowing agents to perform most tracking tasks effectively.