Skip to main content
Glama

get_ephemeris

Compute the apparent ephemeris of solar-system bodies from JPL Horizons, providing ICRS position, distance, range rate, and V magnitude for a specified time window.

Instructions

Compute a solar-system body's apparent ephemeris from JPL Horizons.

Returns a time series of ICRS position, distance (delta, in AU), range rate, and V magnitude for a body such as "99942 Apophis", "Ceres", or "C/2023 A3". observer_location is a Horizons code; "500@399" is geocentric. This is the capability the other astronomy MCP servers skip, so prefer it for "where is

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stepNoSampling step such as 1h, 30m, or 1d1h
stopYesUT stop date, YYYY-MM-DD or YYYY-MM-DD HH:MM
startYesUT start date, YYYY-MM-DD or YYYY-MM-DD HH:MM
targetYes
observer_locationNo500@399

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsNo
targetYes
observerYes
provenanceYes
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: it returns a time series, specifies the data source (JPL Horizons), explains the observer_location parameter with a concrete example ('500@399' for geocentric), and notes that windows exceeding ~2000 samples are rejected. No contradictions.

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?

Four sentences, front-loaded with core purpose, then details, then usage guidance. No wasted words.

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

Completeness5/5

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

Given the tool's complexity (astronomy ephemeris), the presence of an output schema (so return values are covered), and the fact that the description covers purpose, usage, parameters, and limitations, it is fully complete for agent selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning beyond the schema: it explains observer_location as a Horizons code with an example, clarifies step with examples like '1h' or '30m', and gives example targets for the target parameter (e.g., '99942 Apophis'). This compensates for the incomplete schema descriptions (60% coverage).

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 explicitly states it computes a solar-system body's apparent ephemeris from JPL Horizons, listing returned quantities (ICRS position, distance, range rate, V magnitude) and examples of targets. It also distinguishes from siblings by noting this capability is unique among astronomy MCP servers.

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?

The description provides explicit guidance: 'prefer it for "where is <body> on <date>" questions.' It also mentions the sample limit (~2000 samples) which helps agents avoid rejected queries. However, it does not give explicit when-not-to-use scenarios.

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/KarthikSubramanian07/skyquery'

If you have feedback or need assistance with the MCP directory API, please join our Discord server