Skip to main content
Glama

AstroWay Core astrology

Eclipses

astroway_calendar_eclipses
Read-onlyIdempotent

Find solar and lunar eclipses within a given year or multi-year range. Returns type, date, and geographic visibility data.

[Group: Calendar & Cycles] [Endpoint: POST /v1/eclipses] [Required: year] [Cost: 100 credits (Tier 4)]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>"
    },
    "name": "astroway_calendar_eclipses"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
yearsRangeNo

Output Schema

NameRequiredDescriptionDefault
eclipsesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / year / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / year / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / eclipses / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "additionalProperties": {},
      -          "properties": {
      -            "beginDate": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "beginJd": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "endDate": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "endJd": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "kind": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "longitude": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "maxDate": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "maxJd": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "signIndex": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "totalityBeginJd": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "totalityEndJd": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "type": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            }
      -          },
      -          "type": "object"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "beginDate": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "beginJd": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "endDate": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "endJd": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "kind": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "longitude": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "maxDate": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "maxJd": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "signIndex": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "totalityBeginJd": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "totalityEndJd": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "type": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-schema information: the envelope of returned data (type, date, visibility) plus a cost signal ('100 credits, Tier 4'), which matters for an agent budgeting calls. It stops short of describing pagination or how large multi-year result sets behave.

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?

Two front-loaded sentences followed by a compact bracketed metadata block; nothing is padded or repeated. The only inefficiency is that the metadata block restates the required parameter without clarifying its relationship to yearsRange, so that line spends space without resolving the main ambiguity.

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?

With an output schema present, the description is not obliged to enumerate return fields, yet it does so briefly, and annotations carry the safety profile. For a four-parameter lookup tool the only material omission is the year/yearsRange interaction and the maximum span implications of a 20-unit range cap.

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?

Schema coverage is 50%: 'fields' and 'precision' are well documented inline, but 'year' and 'yearsRange' carry no schema description at all. The description partially compensates with 'within a given year or multi-year range', hinting that 'year' is the primary selector and 'yearsRange' extends it, yet it never states the interaction (is 'year' a start year? is it required even with a range?).

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

Purpose4/5

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

Uses a specific verb ('Find') with a specific resource ('solar and lunar eclipses') and states the temporal scope ('within a given year or multi-year range'). It clearly separates itself from computation-heavy neighbours via the returned 'type, date, and geographic visibility data', but never names the closest siblings (astroway_geo_eclipse_analysis, astroway_render_eclipse_path) to prevent confusion.

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

Usage Guidelines3/5

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

The phrase 'within a given year or multi-year range' implicitly tells the agent this is a date-span lookup rather than a single-event detail call, which is useful context. However, there is no explicit when-to-use vs when-not, and no routing to astroway_geo_eclipse_analysis (per-eclipse geometry) or astroway_render_eclipse_path (visualisation) despite those being obvious alternatives in the sibling list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources