Biorhythm MCP Server by RoxyAPI

Get biorhythm reading - Complete cycle analysis for any date

post_biorhythm_reading

Read-only

Calculate a complete biorhythm reading for a given birth date and target date. Returns all 10 cycle values (physical, emotional, intellectual, intuitive, aesthetic, awareness, spiritual, passion, mastery, wisdom), phase detection with 8 distinct states, energy rating (1-10), overall phase assessment, editorial-grade interpretation, actionable advice, and critical day alerts. Perfect for wellness apps, dating platforms, productivity tools, and AI chatbot integrations that need structured biorhythm data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.	en
`compact`	No	Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
`birthDate`	Yes	Birth date of the person in YYYY-MM-DD format. This is the anchor for all biorhythm cycle calculations.
`targetDate`	No	Date to calculate the reading for in YYYY-MM-DD format. Defaults to today (UTC) if omitted.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`advice`	Yes
`cycles`	Yes
`birthDate`	Yes
`targetDate`	Yes
`energyRating`	Yes
`overallPhase`	Yes
`criticalAlerts`	Yes
`daysSinceBirth`	Yes
`interpretation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "advice": {
+      "type": "string"
+    },
+    "birthDate": {
+      "type": "string"
+    },
+    "criticalAlerts": {
+      "items": {
+        "properties": {
+          "advisory": {
+            "type": "string"
+          },
+          "cycle": {
+            "enum": [
+              "physical",
+              "emotional",
+              "intellectual",
+              "intuitive",
+              "aesthetic",
+              "awareness",
+              "spiritual",
+              "passion",
+              "mastery",
+              "wisdom"
+            ],
+            "type": "string"
+          },
+          "direction": {
+            "enum": [
+              "ascending",
+              "descending"
+            ],
+            "type": "string"
+          },
+          "type": {
+            "enum": [
+              "zero_crossing"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "cycle",
+          "type",
+          "direction",
+          "advisory"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "cycles": {
+      "additionalProperties": {
+        "properties": {
+          "dayInCycle": {
+            "type": "number"
+          },
+          "daysUntilCritical": {
+            "type": "number"
+          },
+          "daysUntilPeak": {
+            "type": "number"
+          },
+          "daysUntilTrough": {
+            "type": "number"
+          },
+          "interpretation": {
+            "type": "string"
+          },
+          "phase": {
+            "enum": [
+              "peak",
+              "high",
+              "rising",
+              "critical_ascending",
+              "critical_descending",
+              "falling",
+              "low",
+              "trough"
+            ],
+            "type": "string"
+          },
+          "phaseLabel": {
+            "type": "string"
+          },
+          "rawValue": {
+            "type": "number"
+          },
+          "trend": {
+            "enum": [
+              "rising",
+              "falling",
+              "peaking",
+              "bottoming"
+            ],
+            "type": "string"
+          },
+          "value": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "value",
+          "rawValue",
+          "phase",
+          "phaseLabel",
+          "dayInCycle",
+          "daysUntilPeak",
+          "daysUntilTrough",
+          "daysUntilCritical",
+          "trend",
+          "interpretation"
+        ],
+        "type": "object"
+      },
+      "type": "object"
+    },
+    "daysSinceBirth": {
+      "type": "number"
+    },
+    "energyRating": {
+      "type": "number"
+    },
+    "interpretation": {
+      "type": "string"
+    },
+    "overallPhase": {
+      "enum": [
+        "high_energy",
+        "mixed",
+        "recovery",
+        "critical"
+      ],
+      "type": "string"
+    },
+    "targetDate": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "birthDate",
+    "targetDate",
+    "daysSinceBirth",
+    "cycles",
+    "energyRating",
+    "overallPhase",
+    "interpretation",
+    "advice",
+    "criticalAlerts"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 25, 2026

changedInput schema / properties / lang / description

Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English."

changedInput schema / properties / lang / enum

Previous value: -[
-  "en",
-  "tr",
-  "de",
-  "es",
-  "hi",
-  "pt",
-  "fr",
-  "ru"
-]New value: +[
+  "en",
+  "tr",
+  "de",
+  "es",
+  "hi",
+  "pt",
+  "fr",
+  "ru",
+  "zh-Hans",
+  "zh-Hant"
+]

Changed2 schema fields changedAug 17, 2026

addedInput schema / examples

Added value: +[
+  {
+    "birthDate": "1990-07-15"
+  }
+]

changedInput schema / properties / compact / description

Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {\"__cols\":[names],\"__rows\":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens."

Changed1 schema field changedJul 22, 2026

changedInput schema / properties / compact / description

Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."

Changed1 schema field changedJul 22, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}

First observedJul 8, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds value by detailing the return payload (cycle values, phases, energy rating, advice, alerts), which helps set expectations. It does not contradict annotations. However, it does not disclose any potential edge cases (e.g., date validation, timezone handling) or operational behaviors beyond the fact that it calculates and returns data.

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?

The description is two sentences: the first delivers the core purpose and outputs, the second lists target audiences. It is concise and front-loaded, with no filler. The use-case sentence is slightly marketing-oriented but still useful. It could be trimmed, but overall it is efficient and well-structured.

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

Completeness4/5

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

Given the presence of an output schema (as indicated by context signals) and rich parameter descriptions, the description provides a strong overview of what the tool returns, including the full list of cycle names, phase states, and additional outputs like advice and alerts. It does not mention error handling or edge cases, but these are not strictly required when an output schema exists. The description is sufficient for an agent to understand the tool's scope.

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 each parameter (lang, compact, birthDate, targetDate) already has a thorough description. The tool description only repeats 'birth date and target date' without adding new semantic detail. It does not explain the 'compact' or 'lang' parameters beyond what the schema provides, so it does not meaningfully enhance parameter understanding. Baseline 3 is appropriate.

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

Purpose4/5

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

The description clearly states the tool calculates a complete biorhythm reading for given birth and target dates, and enumerates the specific outputs (10 cycles, phase detection, energy rating, etc.). It is not a tautology and the verb 'Calculate' plus resource 'biorhythm reading' is specific. However, it does not explicitly differentiate itself from sibling tools like post_biorhythm_daily or post_biorhythm_forecast, relying instead on the word 'complete' to imply broader scope.

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

Usage Guidelines3/5

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

The description gives context by listing ideal use cases ('wellness apps, dating platforms, productivity tools, AI chatbot integrations'), which implies when it might be used. But it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or conditions. There is no guidance like 'for a single-day summary use post_biorhythm_daily instead'. This leaves some ambiguity.

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

All Biorhythm MCP Server by RoxyAPI 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?