Asterwise

Biorhythm

asterwise_get_biorhythm

Read-only

Computes physical (23-day), emotional (28-day), and intellectual (33-day) biorhythm cycles for a birth date.

WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_nakshatra_prediction — for the Vedic personalized daily prediction.

INPUT CONTRACT: birth_date (required): Date of birth in YYYY-MM-DD format. target_date (optional): Date to compute for. Defaults to today. days (optional int 1-90): Number of consecutive days. Default 1.

DO NOT CONFUSE WITH: asterwise_get_nakshatra_prediction — Vedic Tarabala/Chandrabala daily prediction. asterwise_get_panchanga — Vedic daily panchanga elements, not biorhythm cycles.

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Number of consecutive days to include, starting from the target date.
`birth_date`	Yes	Date of birth, YYYY-MM-DD.
`target_date`	No	Date to chart the cycles for, YYYY-MM-DD. Defaults to today.
`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. Dates show when Glama detected each change.

Changed4 schema fields changedSep 5, 2026

addedInput schema / properties / birth_date / description
```
Added value: +"Date of birth, YYYY-MM-DD."
```

addedInput schema / properties / days / description

Added value: +"Number of consecutive days to include, starting from the target date."

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 / target_date / description

Added value: +"Date to chart the cycles for, YYYY-MM-DD. Defaults to today."

Changed2 schema fields changedSep 4, 2026
- addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```
- changedInput schema / required
```
Previous value: -[
-  "birth_date",
-  "response_format"
-]New value: +[
+  "birth_date"
+]
```
AddedMay 2, 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 and destructiveHint=false, so no side-effect disclosure is needed. The description adds meaningful context: it is standalone, computes three named cycles, has sensible date/day defaults, and points to a full output and error contract. It does not inline the error contract details, but for a read-only computation this is sufficient.

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 organized into clear labeled sections (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH) with no filler. The core function is front-loaded, and every sentence contributes either a default, a constraint, or a sibling distinction that helps the agent act correctly.

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 tool with one required parameter, fully described schema fields, an output schema, and safety annotations, the description is complete: it covers prerequisites (none), post-steps, defaults, exclusions, and a pointer to the full contract. Nothing necessary for correct selection or invocation is missing.

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 schema already documents every parameter; that sets a baseline of 3. The description adds extra value by restating the required/optional contract, calling out the 1-90 valid range for days (absent from the schema), and confirming defaults for target_date and days.

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 opening sentence uses a specific verb ('Computes') plus a precise resource: physical, emotional, and intellectual biorhythm cycles with their period lengths (23/28/33 days). It also distinguishes itself from asterwise_get_nakshatra_prediction and asterwise_get_panchanga, making it easy to tell apart from the large sibling set.

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 states 'BEFORE: None — standalone' and points to asterwise_get_nakshatra_prediction as a sensible AFTER step. The DO NOT CONFUSE WITH section names two siblings and the condition that selects them, giving the agent clear 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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation3/5

Many tools are well-differentiated by explicit 'DO NOT CONFUSE WITH' notes, but the sheer number of near-neighbor pairs (e.g., crystal vs gemstone recommendations, natal chart variants, dasha systems, compatibility systems, tarot draw variants) creates real selection risk. The descriptions mitigate overlap, but an agent browsing 103 tools will struggle to pick the right one.

Naming Consistency5/5

Every tool follows the asterwise_get_* or asterwise_draw_* prefix convention with a clear noun phrase (e.g., asterwise_get_natal_chart, asterwise_draw_tarot_cards). The two verbs 'get' and 'draw' are semantically appropriate, and there are no camelCase or mixed-style names.

Tool Count1/5

103 tools is far beyond a manageable MCP surface. While the domain is broad (Vedic astrology, Western astrology, numerology, tarot, crystals, dream symbols), the server bundles multiple distinct domains into one namespace, making it nearly impossible for an agent to discover the right tool efficiently.

Completeness4/5

The surface is impressively comprehensive across astrology, numerology, tarot, and remedies, with deep coverage of dasha systems, compatibility frameworks, and chart types. Minor gaps exist (e.g., no tarot interpretation endpoint, no batch operations, no update/delete since it's read-only data), but for a reference/prediction API the coverage is strong.

Resources

Need Help?