Skip to main content
Glama
astroway

astroway-mcp

Official
by astroway

90° Dial

astroway_cosmobiology_dial_90
Read-onlyIdempotent

Calculates all chart points in the 90° cardinal modulus for cosmobiology and Hamburg School analysis from date, time, and coordinates.

Instructions

All chart points in 90° cardinal modulus.

[Group: Cosmobiology / Hamburg School] [Endpoint: POST /v1/cosmobiology/dial-90] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
withTnpNo
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
pointsNo
sourceNo
modulusNo
methodologyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful operational context — endpoint, required inputs, and a 10-credit Tier 1 cost — which an agent needs for budgeting, but says nothing about what the dial output contains or how TNP/ayanamsa options change it.

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?

Compact and front-loaded: the one substantive sentence comes first, followed by clearly delimited bracketed metadata. Little waste, though the bracket lines are boilerplate rather than explanatory content.

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 not be described. But for a 14-parameter, 21%-coverage computation tool with no exclusions or alternatives given, the description is thinner than the tool's complexity warrants.

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 21% across 14 parameters. The description repeats the four required fields but leaves the most consequential optional ones unexplained, notably withTnp (Uranian trans-Neptunian points, central to Hamburg School work) and cosmogram, which materially change the result.

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

Purpose3/5

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

States the resource ('all chart points') and the modulus ('90° cardinal modulus'), which places it in the Cosmobiology family. However it gives no verb and does not distinguish it from near siblings such as astroway_cosmobiology_cosmogram, astroway_render_cosmogram, or astroway_cosmobiology_midpoint_pictures, so an agent could easily pick the wrong dial/cosmogram tool.

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?

Nothing says when to reach for the 90° dial versus the cosmogram, midpoint pictures, or sensitive-points tools. The only guidance is the metadata block listing required fields and cost, which is prerequisite info rather than usage routing.

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