Asterwise

Personal Cycles

asterwise_get_personal_cycles

Read-onlyIdempotent

Returns the Personal Year, Personal Month, and Personal Day numbers for a given birth date and optional target date. All three cycle numbers are derived from the birth month, birth day, and the target calendar date.

WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_numerology_profile — see personal cycles alongside core numbers.

INPUT CONTRACT: date — Birth date in YYYY-MM-DD format. Example: '1985-11-12' year (optional int) — Target year. Defaults to current calendar year. Example: 2026 month (optional int 1–12) — Target month. Defaults to current month. Example: 5 day (optional int 1–31) — Target day. Personal Day is only returned when day is provided. Defaults to null (Personal Day omitted). Example: 1

DO NOT CONFUSE WITH: asterwise_get_personal_year — returns Personal Year only, no month or day breakdown. asterwise_get_numerology_profile — core name numbers; personal_year field is null there.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-personal-cycles/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`day`	No	Day of the month 1-31. Defaults to today when omitted.
`date`	Yes	Date in YYYY-MM-DD format.
`year`	No	Four-digit calendar year, e.g. 2026. Defaults to the current year when omitted.
`month`	No	Month number 1-12. Defaults to the current month when omitted.
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026

changedInput schema / properties / date / description

Previous value: -"Date in YYYY-MM-DD format. Defaults to today when omitted."New value: +"Date in YYYY-MM-DD format."

Changed5 schema fields changedSep 5, 2026

addedInput schema / properties / date / description

Added value: +"Date in YYYY-MM-DD format. Defaults to today when omitted."

addedInput schema / properties / day / description

Added value: +"Day of the month 1-31. Defaults to today when omitted."

addedInput schema / properties / month / description

Added value: +"Month number 1-12. Defaults to the current month when omitted."

addedInput schema / properties / response_format / description

Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."

addedInput schema / properties / year / description

Added value: +"Four-digit calendar year, e.g. 2026. Defaults to the current year when omitted."

Changed2 schema fields changedSep 4, 2026
- addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```
- changedInput schema / required
```
Previous value: -[
-  "date",
-  "response_format"
-]New value: +[
+  "date"
+]
```
AddedMay 1, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to reassert safety. It adds useful behavioral detail beyond annotations: the derivation basis (birth month/day plus target date), the conditional behavior of the day parameter ('Personal Day is only returned when day is provided'), and a link to the full output/error contract. Minor gap: it does not mention response_format behavior, though the schema covers that.

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

Conciseness5/5

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

The description is well-structured with clear labeled sections (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH), front-loaded summary, and concrete examples. Every section adds actionable information; nothing is redundant filler. The link to the full contract avoids bloat while providing a path to complete details.

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?

For a read-only computational tool with an output schema present, the description covers inputs, defaults, conditional behavior, workflow placement, and sibling differentiation. It even provides a link to the complete output/error contract, so nothing critical is missing for the agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds concrete examples and behavioral nuances not in the schema: the day parameter's conditional effect on output, the current-calendar-year default, and the explicit statement that day defaults to null. However, there is an internal inconsistency: the description says day defaults to null and Personal Day is omitted, while the schema says day defaults to today when omitted. This weakens an otherwise strong parameter explanation.

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 description opens with a precise verb and resource: 'Returns the Personal Year, Personal Month, and Personal Day numbers for a given birth date and optional target date.' It clearly distinguishes itself from asterwise_get_personal_year by stating this tool returns all three cycles, not just the year. The 'DO NOT CONFUSE WITH' section further disambiguates from sibling tools.

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

Usage Guidelines5/5

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

The WORKFLOW section explicitly documents placement before and after other tools, and the 'DO NOT CONFUSE WITH' section names specific alternatives with the exact reason to choose this tool instead. This gives the agent explicit when-to-use and when-not-to-use guidance.

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

All Asterwise 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?