Biorhythm MCP Server by RoxyAPI

Get phase info - Lightweight cycle status for dashboards and widgets

post_biorhythm_phases

Read-only

Get current phase information for all 10 biorhythm cycles without the full interpretation payload. Returns value, phase name, phase label, day position within cycle, cycle period, days until next critical crossing, and short-term trend for each cycle. Includes a compact summary string. Designed as a lightweight endpoint for dashboards, widgets, status bars, and quick-check interfaces that need biorhythm phase data without editorial text.

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.
`targetDate`	No	Date to get phase information for in YYYY-MM-DD format. Defaults to today (UTC).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`phases`	Yes
`summary`	Yes
`birthDate`	Yes
`targetDate`	Yes
`daysSinceBirth`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "birthDate": {
+      "type": "string"
+    },
+    "daysSinceBirth": {
+      "type": "number"
+    },
+    "phases": {
+      "additionalProperties": {
+        "properties": {
+          "dayInCycle": {
+            "type": "number"
+          },
+          "daysUntilCritical": {
+            "type": "number"
+          },
+          "phase": {
+            "enum": [
+              "peak",
+              "high",
+              "rising",
+              "critical_ascending",
+              "critical_descending",
+              "falling",
+              "low",
+              "trough"
+            ],
+            "type": "string"
+          },
+          "phaseLabel": {
+            "type": "string"
+          },
+          "totalDays": {
+            "type": "number"
+          },
+          "trend": {
+            "enum": [
+              "rising",
+              "falling",
+              "peaking",
+              "bottoming"
+            ],
+            "type": "string"
+          },
+          "value": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "value",
+          "phase",
+          "phaseLabel",
+          "dayInCycle",
+          "totalDays",
+          "daysUntilCritical",
+          "trend"
+        ],
+        "type": "object"
+      },
+      "type": "object"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "targetDate": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "birthDate",
+    "targetDate",
+    "daysSinceBirth",
+    "phases",
+    "summary"
+  ],
+  "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

A4.3/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 the safety profile is covered. The description adds useful behavioral context by disclosing the lightweight/compact nature, the exclusion of editorial interpretation, and the presence of a compact summary string. It does not add unrelated details like auth or rate limits, which are not critical here.

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?

Three tight sentences with no filler. The first sentence front-loads the core purpose and key differentiator, the second enumerates the returned fields, and the third names the intended audience. Every sentence earns its place.

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 an output schema present and safety annotations already covering read-only behavior, the description sufficiently covers what the tool does, what it returns, and when to use it. An agent has everything needed to invoke and interpret this endpoint correctly.

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 schema already fully documents parameters like birthDate, targetDate, lang, and compact. The description adds no parameter-specific guidance beyond what the schema provides, which aligns with the baseline score of 3.

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 states a specific verb and resource: 'Get current phase information for all 10 biorhythm cycles.' It clearly differentiates from siblings by emphasizing the lightweight payload, 'without the full interpretation payload,' which distinguishes it from fuller endpoints like post_biorhythm_reading or post_biorhythm_forecast.

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?

The description provides a clear intended-use context: dashboards, widgets, status bars, and quick-check interfaces that need phase data without editorial text. It stops short of explicitly naming alternatives or stating when not to use it, but the use-case framing is strong enough for an agent to select it appropriately.

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?