Skip to main content
Glama
igmizo

auseklis

by igmizo

Find Eclipses

find_eclipses
Read-onlyIdempotent

Find lunar and solar eclipses within a date range, including astrological sign and longitude. Optionally check visibility of solar eclipses from a specific location.

Instructions

Find lunar and solar eclipses in a date range (max 30 years), with the sign and longitude of the eclipsed luminary — the astrologically relevant datum.

When latitude/longitude are provided, each solar eclipse also reports whether it is visible from that location and how much of the Sun is obscured there.

Examples:

  • "Eclipses in 2026" -> { from_datetime: "2026-01-01", to_datetime: "2027-01-01" }

  • "Will I see the August 2026 eclipse from Riga?" -> add latitude: 56.95, longitude: 24.11

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_datetimeYesStart of the search window.
to_datetimeYesEnd of the search window (max 30 years after start).
typesNoRestrict to lunar or solar eclipses. Default: both.
latitudeNoObserver latitude for local solar-eclipse visibility.
longitudeNoObserver longitude for local solar-eclipse visibility.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
eclipsesYes
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds important operational details: maximum 30-year range, and solar eclipse visibility when latitude/longitude are provided. No contradictions 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 concise (5 sentences) and well-structured: opening with purpose, then constraints, optional parameter behavior, and examples. Every sentence adds useful information without redundancy.

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 (eclipses, visibility, astrological relevance) and the presence of a complete schema and annotations, the description covers all necessary aspects: main function, constraints, optional features, and usage examples. No gaps identified.

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

Parameters4/5

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

With 100% schema coverage, baseline is 3. The description adds value by explaining the purpose of latitude/longitude for visibility and providing concrete examples that clarify parameter usage beyond the schema.

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 finds lunar and solar eclipses within a date range and mentions the astrological relevance (sign and longitude of eclipsed luminary). This distinguishes it from sibling tools which compute charts, transits, or aspects, not eclipses.

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 context on when to use the tool (finding eclipses in a date range) and gives examples that illustrate typical queries. However, it does not explicitly state when not to use it or mention alternatives among siblings, which would improve guidance.

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/igmizo/auseklis'

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