Skip to main content
Glama
astroway

astroway-mcp

Official
by astroway

Sphaera Barbarica

astroway_hellenistic_greenbaum_sphaera_barbarica
Read-onlyIdempotent

Calculate Hellenistic Greenbaum constellations outside the zodiac from date, time, latitude, and longitude to map the barbaric sphere.

Instructions

Constellations beyond the zodiac.

[Group: Hellenistic: Greenbaum tradition] [Endpoint: POST /v1/hellenistic/greenbaum/sphaera-barbarica] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
latitudeYes
timezoneNoIANA 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.
cosmogramNo
longitudeYes
ayanamsaIdNo
zodiacTypeNo
houseSystemNoP
timezoneOffsetNoHours 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

NameRequiredDescriptionDefault
notesNo
anglesNo
sourceNo
doctrineNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare a read-only, idempotent, non-destructive, closed-world operation. The description adds only the credit cost and a required-parameter list; it does not explain the computation, what the 'constellations beyond the zodiac' output represents, or any special constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, but it is under-specified rather than concise. The only substantive content is a four-word fragment, with the rest being template boilerplate.

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

Completeness2/5

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

For a 13-parameter Hellenistic computation with low schema description coverage, this description is far too thin. An output schema and annotations exist, but the description does not explain the technique, the role of the required birth data, or how optional astrological settings affect results.

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 23% across 13 parameters. The description names the four required inputs but provides no meaning, format, or interaction details for important optional parameters such as ayanamsa, zodiacType, houseSystem, or cosmogram.

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

Purpose2/5

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

The description is a topic fragment, 'Constellations beyond the zodiac,' not a verb-plus-resource statement of what the tool computes or returns. It hints at parazodiacal constellations but does not distinguish this from siblings such as astroway_aspects_fixed_stars or astroway_geo_parans_star.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, when not to, or which sibling to choose instead. The boilerplate group/endpoint/required lines are structural metadata, not usage instructions.

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