Skip to main content
Glama
IBM

chuk-mcp-celestial

by IBM

get_planet_events

Calculate rise, set, and transit times for planets at your location to plan optimal observation sessions.

Instructions

Get rise, set, and transit times for a planet on a given day at a location.

Returns the times a planet rises above the horizon, transits the meridian (highest point), and sets below the horizon. Essential for planning when to observe a planet.

Args: planet: Planet name. One of: Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune, Pluto date: Date in YYYY-MM-DD format (e.g., "2025-6-15") latitude: Observer's latitude in decimal degrees (-90 to 90) longitude: Observer's longitude in decimal degrees (-180 to 180) timezone: Timezone offset from UTC in hours (e.g., -8 for PST). When provided, event times are in local time. dst: Whether to apply daylight saving time adjustment.

Returns: PlanetEventsResponse: GeoJSON Feature containing: - geometry: Observer location - properties.data: - planet: Planet name - date: Query date - events: List of rise/set/transit events with times - constellation: Current constellation - magnitude: Apparent visual magnitude - artifact_ref: Reference to stored computation (if artifact store configured)

Tips for LLMs: - Events may be empty if the planet doesn't rise/set that day (polar regions) - Transit time is when the planet is highest — best viewing time - Use with get_planet_position to get full details at a specific time - Outer planets (Jupiter, Saturn) are above the horizon for ~12 hours - Inner planets (Mercury, Venus) are only visible near sunrise or sunset

Example: events = await get_planet_events( planet="Jupiter", date="2025-6-15", latitude=51.5, longitude=-0.1, timezone=1 ) for event in events.properties.data.events: print(f"Jupiter {event.phen} at {event.time}")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planetYes
dateYes
latitudeYes
longitudeYes
timezoneNo
dstNo
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does an excellent job describing what the tool returns (GeoJSON Feature with specific properties), edge cases ('Events may be empty if the planet doesn't rise/set that day'), and practical implications ('Transit time is when the planet is highest — best viewing time'). It also mentions artifact storage behavior when configured.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (purpose, args, returns, tips, example) and front-loaded with the core functionality. While comprehensive, every sentence earns its place by providing essential information. The example is particularly helpful for understanding usage patterns.

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 (6 parameters, astronomical calculations) and lack of both annotations and output schema, the description provides complete context. It explains what the tool does, how to use it, what parameters mean, what to expect in return, edge cases, and relationships to sibling tools. The return value documentation effectively substitutes for a missing output schema.

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?

With 0% schema description coverage, the description fully compensates by providing comprehensive parameter documentation. Each of the 6 parameters is clearly explained with examples, valid values, ranges, and practical meaning. The description adds significant value beyond what the bare schema provides, including enumerated planet names, date format examples, coordinate ranges, and timezone usage details.

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 clearly states the tool's purpose with specific verbs ('Get rise, set, and transit times') and resources ('for a planet on a given day at a location'). It distinguishes from siblings by focusing specifically on planetary events rather than seasons, moon phases, positions, or other astronomical data.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus alternatives: 'Use with get_planet_position to get full details at a specific time' directly names a sibling tool for complementary use. The 'Tips for LLMs' section offers additional context about when events might be empty and viewing characteristics of different planet types.

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/IBM/chuk-mcp-celestial'

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