Skip to main content
Glama
ganguoguo444004-coder

cosine-astro-mcp

by ganguoguo444004-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Annual profection

annual_profection
Read-onlyIdempotent

Compute Hellenistic annual profections for a birth date and age or target date: find the profected house, sign, lord of the year, and the dates that profection year covers.

Instructions

Hellenistic annual profection for an age or a date: the profected house (whole-sign, counted from the Ascendant; from the Sun's sign if the birth time is unknown), its sign, the lord of the year (traditional ruler, with the modern co-ruler) and where that lord sits in the natal chart, plus the dates the profection year runs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageNoAge in completed years. Takes precedence over `on_date`.
cityNoOptional shortcut: a city from the built-in offline table (about 110 large cities, English or Chinese name, e.g. "Beijing", "上海", "London", "New York"). Explicit latitude/longitude/timezone override it. For anywhere else, pass coordinates.
dateYesBirth date (local calendar date), YYYY-MM-DD
timeNoLocal clock time of birth, 24-hour HH:MM. Omit if unknown: planets are then cast for local noon and there are no Ascendant, Midheaven or houses.
on_dateNoDate to find the profection year for, YYYY-MM-DD (default: today in the birth time zone)
latitudeNoBirthplace latitude in degrees, north positive
timezoneNoIANA time zone of the birthplace, e.g. "Asia/Shanghai", "America/New_York". Historical daylight saving time is applied automatically. Required unless `city` is given.
longitudeNoBirthplace longitude in degrees, east positive (New York is about -74.0)
house_systemNoHouse system. Placidus (default) falls back to whole-sign inside the polar circles, where it has no solution.placidus

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuine domain behavior: the whole-sign counting rule, the Sun-sign fallback when the birth time is absent, and the traditional-ruler-plus-modern-co-ruler convention. It does not discuss return format mechanics, but the substantive behavior is disclosed.

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?

A single front-loaded sentence that opens with the purpose and then unpacks the returns; no filler. It is dense with stacked clauses, which is efficient but slightly hard to scan compared to a split form.

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

Completeness5/5

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

With no output schema and nine parameters, the description carries the return-value burden and discharges it by enumerating the house, sign, lord of the year, lord's location, and date range. Nothing an agent needs to decide to call it or interpret results is missing.

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?

Schema coverage is 100%, so every parameter (age, on_date, city, time, timezone, house_system, etc.) is already documented in the schema, including age's precedence over on_date. The description only restates the age-or-date framing and the unknown-birth-time behavior, so the baseline 3 is appropriate.

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?

Names a specific technique (Hellenistic annual profection) and enumerates exactly what it computes: profected house, its sign, lord of the year with modern co-ruler, the lord's natal placement, and the year's start/end dates. It is unmistakably distinct from siblings like natal_chart or transits.

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

Usage Guidelines4/5

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

States it can be run 'for an age or a date' and gives the key conditional: whole-sign from the Ascendant, or from the Sun's sign if birth time is unknown. It does not explicitly route against the sibling tools (transits, natal_chart), so it falls short of a full when/when-not statement.

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