Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Star-planet parans (Brady)

astroway_geo_parans_star
Read-onlyIdempotent

Calculate exact latitudes where a fixed star and a planet are simultaneously angular, returning star-planet paran event pairs and house roles for a chart moment.

Instructions

Latitudes where a fixed star and a planet are angular at the same moment, which is how Brady tabulates a paran: not a place, a latitude. Twelve event pairs per star and planet (rise, set, culminate, anticulminate, minus meridian against meridian, which is a shared right ascension rather than a paran). Each row carries the houses of the technique in plain form: which body does what, the latitude, and the meridian where it happens at this chart moment. Solved on hour angles rather than by intersecting map polylines, so the latitude is exact rather than quantised to the polyline step.

[Group: Astro-Geography] [Endpoint: POST /v1/parans/star] [Cost: 50 credits (Tier 3)]

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": {
      "body": "<body>"
    },
    "name": "astroway_geo_parans_star"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesBirth data for star-planet parans. Coordinates are not used: a paran is a latitude, and which latitudes exist depends on the moment, not on where the native was born.

Output Schema

NameRequiredDescriptionDefault
gmstNo
noteNo
typeNo
countNo
starsNo
paransNo
horizonNo
julianDayNo
obliquityNo
latitudeLimitNo
starsWithNoParansNo
requestedStarsNotFoundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.1
    • changedInput schema / properties / body / allOf
      Previous value: -[
      -  {
      -    "additionalProperties": {
      -      "anyOf": [
      -        {},
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "description": "Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems.",
      -    "properties": {
      -      "ayanamsa": {
      -        "description": "Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.",
      -        "enum": [
      -          "fagan-bradley",
      -          "lahiri",
      -          "de-luce",
      -          "raman",
      -          "krishnamurti",
      -          "kp",
      -          "yukteshwar",
      -          "jn-bhasin",
      -          "true-citra",
      -          "djwhal-khul"
      -        ],
      -        "type": "string"
      -      },
      -      "ayanamsaId": {
      -        "type": [
      -          "number",
      -          "null"
      -        ]
      -      },
      -      "city": {
      -        "default": "",
      -        "type": "string"
      -      },
      -      "cosmogram": {
      -        "type": "boolean"
      -      },
      -      "date": {
      -        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      -        "type": "string"
      -      },
      -      "houseSystem": {
      -        "default": "P",
      -        "enum": [
      -          "P",
      -          "K",
      -          "R",
      -          "C",
      -          "E",
      -          "W",
      -          "B",
      -          "M",
      -          "O",
      -          "A",
      -          "T",
      -          "V",
      -          "D",
      -          "F",
      -          "G",
      -          "H",
      -          "I",
      -          "i",
      -          "L",
      -          "N",
      -          "Q",
      -          "S",
      -          "U",
      -          "X",
      -          "Y"
      -        ],
      -        "type": "string"
      -      },
      -      "latitude": {
      -        "maximum": 90,
      -        "minimum": -90,
      -        "type": "number"
      -      },
      -      "longitude": {
      -        "maximum": 180,
      -        "minimum": -180,
      -        "type": "number"
      -      },
      -      "name": {
      -        "default": "",
      -        "type": "string"
      -      },
      -      "time": {
      -        "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
      -        "type": "string"
      -      },
      -      "timezone": {
      -        "description": "IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.",
      -        "type": "string"
      -      },
      -      "timezoneOffset": {
      -        "anyOf": [
      -          {
      -            "maximum": 14,
      -            "minimum": -14,
      -            "type": "number"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": 0,
      -        "description": "Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent."
      -      },
      -      "zodiacType": {
      -        "enum": [
      -          "tropical",
      -          "sidereal"
      -        ],
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "date",
      -      "time",
      -      "latitude",
      -      "longitude"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": {
      -      "anyOf": [
      -        {},
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "properties": {
      -      "horizon": {
      -        "description": "Which horizon counts as rising. `geometric` (default) is altitude 0, the semi-diurnal arc as written in Meeus. `apparent` puts it at -34 arcmin, where refraction lifts a body into view first. Worth about two degrees of paran latitude at mid-latitudes, and refraction also breaks the equator mirror that the geometric horizon has, so it is a choice rather than a detail.",
      -        "enum": [
      -          "geometric",
      -          "apparent"
      -        ],
      -        "type": "string"
      -      },
      -      "latitudeLimit": {
      -        "description": "Search range either side of the equator, degrees. Default 60, which is the range Brady tabulates.",
      -        "maximum": 85,
      -        "minimum": 5,
      -        "type": "number"
      -      },
      -      "planets": {
      -        "description": "Swiss Ephemeris planet ids. Default: 0-9, Sun through Pluto.",
      -        "items": {
      -          "anyOf": [
      -            {
      -              "maximum": 9007199254740991,
      -              "minimum": -9007199254740991,
      -              "type": "integer"
      -            },
      -            {
      -              "type": "null"
      -            }
      -          ]
      -        },
      -        "maxItems": 20,
      -        "minItems": 1,
      -        "type": "array"
      -      },
      -      "stars": {
      -        "description": "Star names from the Swiss Ephemeris catalogue. Default: the 36-star astrological set.",
      -        "items": {
      -          "type": "string"
      -        },
      -        "maxItems": 80,
      -        "minItems": 1,
      -        "type": "array"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {
      +      "anyOf": [
      +        {},
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "description": "Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single house-system letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems.",
      +    "properties": {
      +      "ayanamsa": {
      +        "description": "Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.",
      +        "enum": [
      +          "fagan-bradley",
      +          "lahiri",
      +          "de-luce",
      +          "raman",
      +          "krishnamurti",
      +          "kp",
      +          "yukteshwar",
      +          "jn-bhasin",
      +          "true-citra",
      +          "djwhal-khul"
      +        ],
      +        "type": "string"
      +      },
      +      "ayanamsaId": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "city": {
      +        "default": "",
      +        "type": "string"
      +      },
      +      "cosmogram": {
      +        "type": "boolean"
      +      },
      +      "date": {
      +        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +        "type": "string"
      +      },
      +      "houseSystem": {
      +        "default": "P",
      +        "enum": [
      +          "P",
      +          "K",
      +          "R",
      +          "C",
      +          "E",
      +          "W",
      +          "B",
      +          "M",
      +          "O",
      +          "A",
      +          "T",
      +          "V",
      +          "D",
      +          "F",
      +          "G",
      +          "H",
      +          "I",
      +          "i",
      +          "L",
      +          "N",
      +          "Q",
      +          "S",
      +          "U",
      +          "X",
      +          "Y"
      +        ],
      +        "type": "string"
      +      },
      +      "latitude": {
      +        "maximum": 90,
      +        "minimum": -90,
      +        "type": "number"
      +      },
      +      "longitude": {
      +        "maximum": 180,
      +        "minimum": -180,
      +        "type": "number"
      +      },
      +      "name": {
      +        "default": "",
      +        "type": "string"
      +      },
      +      "time": {
      +        "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
      +        "type": "string"
      +      },
      +      "timezone": {
      +        "description": "IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.",
      +        "type": "string"
      +      },
      +      "timezoneOffset": {
      +        "anyOf": [
      +          {
      +            "maximum": 14,
      +            "minimum": -14,
      +            "type": "number"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": 0,
      +        "description": "Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent."
      +      },
      +      "zodiacType": {
      +        "enum": [
      +          "tropical",
      +          "sidereal"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "date",
      +      "time",
      +      "latitude",
      +      "longitude"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": {
      +      "anyOf": [
      +        {},
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "properties": {
      +      "horizon": {
      +        "description": "Which horizon counts as rising. `geometric` (default) is altitude 0, the semi-diurnal arc as written in Meeus. `apparent` puts it at -34 arcmin, where refraction lifts a body into view first. Worth about two degrees of paran latitude at mid-latitudes, and refraction also breaks the equator mirror that the geometric horizon has, so it is a choice rather than a detail.",
      +        "enum": [
      +          "geometric",
      +          "apparent"
      +        ],
      +        "type": "string"
      +      },
      +      "latitudeLimit": {
      +        "description": "Search range either side of the equator, degrees. Default 60, which is the range Brady tabulates.",
      +        "maximum": 85,
      +        "minimum": 5,
      +        "type": "number"
      +      },
      +      "planets": {
      +        "description": "Planet ids: 0 Sun, 1 Moon, 2 Mercury, 3 Venus, 4 Mars, 5 Jupiter, 6 Saturn, 7 Uranus, 8 Neptune, 9 Pluto. Default: 0-9.",
      +        "items": {
      +          "anyOf": [
      +            {
      +              "maximum": 9007199254740991,
      +              "minimum": -9007199254740991,
      +              "type": "integer"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "maxItems": 20,
      +        "minItems": 1,
      +        "type": "array"
      +      },
      +      "stars": {
      +        "description": "Star names from our fixed-star catalogue (GET /reference/fixed-stars). Default: the 36-star astrological set.",
      +        "items": {
      +          "type": "string"
      +        },
      +        "maxItems": 80,
      +        "minItems": 1,
      +        "type": "array"
      +      }
      +    },
      +    "type": "object"
      +  }
      +]
  2. Addedv1.6.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive), so the description adds genuinely new behavioral context: 50 credits at Tier 3, twelve event pairs per pairing, an explicit statement that meridian-against-meridian is a shared right ascension and therefore excluded, and the method (hour angles) that makes the latitude exact rather than quantised to a polyline step. That precision claim is real information an agent could not get from the annotations.

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?

Front-loaded with the definition before the mechanics, and every sentence carries weight except the somewhat vague 'houses of the technique in plain form', which is the only soft phrase. Slightly dense but appropriately sized for a non-obvious domain concept.

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?

For a read-only computational endpoint with a full output schema and exhaustive parameter descriptions, the description covers the concept, the counting convention and the computational method, which is what an agent needs to select it. The one gap is that it never points at the required star catalogue reference or explains that birth coordinates are unused at the description level, both of which live in the schema.

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?

With 100% schema description coverage, the schema already documents stars, planets, horizon, latitudeLimit and the birth-data block in detail, so the baseline is 3. The description adds only marginal parameter meaning — the star/planet pairing count and the per-row contents — and says nothing about the horizon or latitudeLimit choices that materially shift results, leaving the enrichment to 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 opening sentence gives a precise verb-and-resource definition — 'latitudes where a fixed star and a planet are angular at the same moment' — and explicitly corrects the likely misconception with 'not a place, a latitude', which separates it from the location-based geo siblings. The event-pair count and row contents make the output shape concrete enough to distinguish it from a generic parans listing.

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?

Usage is implied rather than stated: the tool is for star-planet parans, so an agent can infer it should use it when stars are involved, and the parenthetical 'rather than a paran' hints at an exclusion. But there is no explicit when-to-use versus astroway_geo_parans, no prerequisite call (e.g. fetching star names from the catalogue) named in the description, and no guidance on when a star paran is the right technique versus an ACG or local-space tool.

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

Deploy Server

Other Tools