Skip to main content
Glama

AstroWay Core astrology

Planetary Cycles

astroway_calendar_planetary_cycles
Read-onlyIdempotent

Find all conjunctions between two planets within a date range, defining the start of a new synodic cycle.

[Group: Calendar & Cycles] [Endpoint: POST /v1/planetary-cycles] [Required: planet1Id, planet2Id, startDate, endDate] [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": {
      "planet1Id": "<planet1Id>",
      "planet2Id": "<planet2Id>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "astroway_calendar_planetary_cycles"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
conjunctionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / planet1Id / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / planet1Id / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedInput schema / properties / planet2Id / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / planet2Id / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / conjunctions / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "additionalProperties": {},
      -          "properties": {
      -            "date": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "jd": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "longitude": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "planet1Id": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "planet2Id": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "signIndex": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            }
      -          },
      -          "type": "object"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "date": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "jd": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "longitude": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "planet1Id": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "planet2Id": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "signIndex": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

B3.2/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 useful operational context the annotations do not: the endpoint, the exact required parameter set, and a 100-credit Tier 4 cost that lets an agent reason about budget before calling. It does not describe result volume or ordering, which is a minor remaining gap.

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 purpose sentence is front-loaded and the bracketed metadata lines are scannable, with no filler prose. The bracketed blocks are slightly redundant with the schema's required list, but they are compact and easy to parse. Nothing here is padded.

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

Completeness3/5

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

With an output schema present, return values need not be explained, and the annotations cover safety. What is missing for a six-parameter tool is any explanation of the planet identifier scheme and of how the conjunction list is bounded or ordered. The credit cost and endpoint are helpful, but the semantic core of the inputs is left to the caller to guess.

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

Parameters2/5

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

Schema description coverage is only 33%, so the description needs to carry weight, but it merely restates the four required parameter names already enforced by the schema. It adds no meaning about what planet IDs refer to (numbering scheme, valid ranges) or how the date range bounds the search. Only 'fields' and 'precision' are documented in the schema itself, leaving the core inputs semantically opaque.

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?

The description states a specific verb and resource: find conjunctions between two named planets over a date range, framed as the start of a synodic cycle. That framing distinguishes it in spirit from siblings like astroway_calendar_planetary_phases or astroway_calendar_cyclic_index, though it never names them. It is clear what the tool returns conceptually.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance, and no named alternative. An agent deciding between this tool and astroway_calendar_planetary_phases, astroway_calendar_cyclic_index, or astroway_calendar_aspects gets no routing signal from the description. The phrase 'defining the start of a new synodic cycle' hints at a use case but does not establish a selection rule.

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