AstroWay Hellenistic and traditional

Stations & Phases

astroway_hels_stations_and_phases

Read-onlyIdempotent

Heliacal phases and stations.

[Group: Hellenistic: Schmidt tradition] [Endpoint: POST /v1/hellenistic/schmidt/stations-and-phases] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]

(Cursor-friendly alias for astroway_hellenistic_schmidt_stations_and_phases.)

Input Schema

Name	Required	Description	Default
`city`	No
`date`	Yes
`name`	No
`time`	Yes
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`ayanamsa`	No	Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
`latitude`	Yes
`timezone`	No	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.
`cosmogram`	No
`longitude`	Yes
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`ayanamsaId`	No
`zodiacType`	No
`houseSystem`	No		P
`timezoneOffset`	No	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.

Output Schema

Name	Required	Description	Default
`source`	No
`doctrine`	No
`perPlanet`	No
`disclaimer`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read. The description adds the credit cost (10 credits, Tier 1) and the endpoint, which annotations do not carry. It stops short of describing what the calculation returns or any limits on the date range.

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-loads the purpose in the first clause, then packs metadata into bracketed lines. No wasted prose, though the bracketed bookkeeping is dense.

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?

An output schema exists, so return values need no explanation, and cost/endpoint/required fields are covered. However, for a 15-parameter tool with low schema coverage, the definition leaves the agent guessing about the optional inputs and when this tool is the right choice.

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% across 15 parameters, so the description should compensate but does not. It merely restates the four required fields already listed in the schema and adds nothing about the condition-sensitive optional parameters such as ayanamsa, houseSystem, or zodiacType.

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?

States a specific resource ('heliacal phases and stations') and situates it in the Schmidt tradition group, which distinguishes it from the other Hellenistic sibling families. There is no explicit verb, but the calculation is named precisely enough. The alias note ties it to `astroway_hellenistic_schmidt_stations_and_phases`, aiding disambiguation.

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?

No statement of when to reach for this rather than the canonical tool or any other Hellenistic sibling. The description gives endpoint, cost, and required inputs but no usage context, prerequisites, or exclusions.

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

All AstroWay Hellenistic and traditional tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?