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/

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>"
    },
    "name": "asterwise_get_personal_cycles"
  }
}

Input Schema

Name	Required	Description	Default
`day`	No	Target day of the month 1-31. Personal Day is returned only when day is given; omit it to get Personal Year and Personal Month only.
`date`	Yes	Date in YYYY-MM-DD format.
`year`	No	Four-digit target year, e.g. 2026. Defaults to the current year (UTC).
`month`	No	Target month 1-12. Defaults to the current month (UTC).
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 10, 2026

changedInput schema / properties / day / description

Previous value: -"Day of the month 1-31. Defaults to today when omitted."New value: +"Target day of the month 1-31. Personal Day is returned only when day is given; omit it to get Personal Year and Personal Month only."

changedInput schema / properties / month / description

Previous value: -"Month number 1-12. Defaults to the current month when omitted."New value: +"Target month 1-12. Defaults to the current month (UTC)."

changedInput schema / properties / year / description

Previous value: -"Four-digit calendar year, e.g. 2026. Defaults to the current year when omitted."New value: +"Four-digit target year, e.g. 2026. Defaults to the current year (UTC)."

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.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it explains how the three numbers are derived and that Personal Day is conditionally omitted when day is not supplied. It does not cover auth needs, limits, or error behavior (deferred to the docs URL), so it falls short of a 5.

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?

Sections are clearly labeled and front-loaded (purpose first, then workflow, contract, disambiguation), which is good for scanning. The per-parameter examples and repeated defaults duplicate schema content, making it slightly longer than strictly necessary.

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?

Given a 5-parameter tool with an output schema present, the description need not explain return values and points to the full output/error contract instead. Workflow position, sibling disambiguation, and input contract are all covered, so nothing essential 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 description coverage is 100%, so the baseline is 3. The INPUT CONTRACT adds examples, ranges, and the conditional return of Personal Day, but largely restates what the schema already documents. It adds marginal meaning over the structured fields.

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 first sentence states a specific verb ('Returns') and the exact resources (Personal Year, Personal Month, Personal Day) along with the scope (birth date + optional target date). The 'DO NOT CONFUSE WITH' section explicitly distinguishes it from asterwise_get_personal_year and asterwise_get_numerology_profile, so an agent can route unambiguously.

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 block states it is standalone (BEFORE: None) and names the natural follow-up tool (asterwise_get_numerology_profile). The 'DO NOT CONFUSE WITH' block gives explicit when-not conditions with reasons, leaving nothing to inference.

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

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?