Skip to main content
Glama

N2yo

by io.github.pipeworx-io

Get Positions

get_positions
Read-onlyIdempotent

Track where a satellite is right now (or in the next few seconds): get its live latitude, longitude, altitude, and look-angles (azimuth/elevation) from an observer on Earth. Use this to answer "where is the ISS right now?" (NORAD id 25544) or to locate any satellite by NORAD id. Example: get_positions({ norad_id: 25544, lat: 40.71, lon: -74.0 }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesObserver latitude in decimal degrees.
lonYesObserver longitude in decimal degrees.
_apiKeyNoOptional — your own N2YO API key for higher limits; omit to use the shared Pipeworx key.
secondsNoNumber of future seconds of positions to predict (default 2, max 300).
altitudeNoObserver altitude in meters above sea level (default 0).
norad_idYesNORAD catalog id of the satellite, e.g. 25544 for the ISS, 20580 for Hubble.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "lat": 40.71,
+    "lon": -74,
+    "norad_id": 25544
+  },
+  {
+    "altitude": 100,
+    "lat": 51.5,
+    "lon": 0,
+    "norad_id": 20580,
+    "seconds": 60
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds useful behavioral context beyond annotations: it specifies the output fields (lat/lon/altitude/look-angles), the 'right now or next few seconds' temporal scope, and the observer-based calculation. No contradiction with 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 two sentences plus a short example. It front-loads the primary purpose and output, then provides a concrete usage example. Every sentence contributes value without redundancy or filler.

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

Completeness4/5

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

Given the 6-parameter schema with full coverage and strong annotations, this description is adequately complete. It states the return fields (useful because there is no output schema), provides a concrete example, and covers the common use case. It does not explain edge cases (invalid NORAD IDs, rate limits), but that is not essential for a simple read-only lookup tool.

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 covers 100% of parameters with descriptions, so the baseline is 3. The description adds an example call and example NORAD IDs, but does not add new semantic meaning beyond what the schema already provides. It does demonstrate parameter usage, which is mildly helpful.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('track'/'get') and clearly identifies the resource ('satellite positions') with concrete outputs (latitude, longitude, altitude, look-angles). It also includes a concrete example (ISS, NORAD 25544), which distinguishes it from sibling tools like get_visual_passes by emphasizing current/now positions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context with 'Use this to answer "where is the ISS right now?"' and explains the general use case (locate any satellite by NORAD id). It does not explicitly mention when not to use it or alternative tools, but the context is sufficient for typical AI selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All N2yo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation2/5

Multiple tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-duplicates (beta is currently identical), and the five Polymarket tools (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) require careful reading to distinguish. Additionally, entity_profile, compare_entities, and recent_changes all handle company data, and ai_visibility_check vs scan_competitor_ai_presence are clearly paired. The detailed descriptions help, but an agent will frequently misselect among these clusters.

Naming Consistency3/5

All names are lowercase with underscores, so the style is internally consistent. However, the pattern is mixed: many use verb_noun (get_positions, list_subscriptions, resolve_entity) but several are noun-first or noun-only (entity_profile, polymarket_edges, pipeworx_trending, bet_research). There's no strong verb/noun convention across the set, making the naming pattern less predictable than it could be.

Tool Count2/5

With 34 tools, the set exceeds the 16–25 'heavy' range and sits in the 'too many' band. The server name suggests a focused satellite-tracking service, yet only 3 tools (get_positions, get_visual_passes, whats_above) serve that purpose; the other 31 cover unrelated domains like data research, prediction markets, memory, and subscriptions. Even as a general-purpose research platform, the count feels bloated and unfocused.

Completeness3/5

The tool surface is broad, covering satellite tracking, data research, prediction markets, subscriptions, and memory, and within each cluster the main operations exist (e.g., subscription lifecycle, edge analysis + fill risk). However, the scattered scope creates gaps: there's no direct raw-data fetch tool (everything goes through ask_pipeworx), no general web search, and the presence of unrelated utilities (generate_llms_txt, scan_dependency) suggests the domain boundaries are unclear. For its stated satellite purpose, the satellite tools are thin (no TLE, no catalog, no detailed orbit info).

Resources