Biorhythm MCP Server by RoxyAPI

Calculate compatibility - Biorhythm alignment between two people

post_biorhythm_compatibility

Read-only

Calculate biorhythm compatibility between two people by overlaying their cycle profiles on a target date. Returns per-cycle alignment scores (0-100) for physical, emotional, and intellectual cycles, an overall compatibility score, relationship rating, strengths, challenges, practical advice, and a daily sync snapshot showing the absolute difference in each primary cycle. Perfect for dating apps, relationship platforms, team-building tools, and couples coaching applications.

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.
`person1`	Yes
`person2`	Yes
`targetDate`	No	Date to evaluate compatibility on in YYYY-MM-DD format. Defaults to today (UTC). Compatibility varies by day since biorhythm cycles are continuous.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`advice`	Yes
`cycles`	Yes
`rating`	Yes
`person1`	Yes
`person2`	Yes
`dailySync`	Yes
`strengths`	Yes
`challenges`	Yes
`targetDate`	Yes
`overallScore`	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"
+    },
+    "challenges": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "cycles": {
+      "additionalProperties": {
+        "properties": {
+          "alignment": {
+            "type": "number"
+          },
+          "description": {
+            "type": "string"
+          },
+          "difference": {
+            "type": "number"
+          },
+          "person1Value": {
+            "type": "number"
+          },
+          "person2Value": {
+            "type": "number"
+          },
+          "phase": {
+            "enum": [
+              "in_sync",
+              "complementary",
+              "neutral",
+              "opposing"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "person1Value",
+          "person2Value",
+          "difference",
+          "alignment",
+          "phase",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "object"
+    },
+    "dailySync": {
+      "properties": {
+        "emotionalDiff": {
+          "type": "number"
+        },
+        "intellectualDiff": {
+          "type": "number"
+        },
+        "physicalDiff": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "physicalDiff",
+        "emotionalDiff",
+        "intellectualDiff"
+      ],
+      "type": "object"
+    },
+    "overallScore": {
+      "type": "number"
+    },
+    "person1": {
+      "properties": {
+        "birthDate": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "birthDate"
+      ],
+      "type": "object"
+    },
+    "person2": {
+      "properties": {
+        "birthDate": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "birthDate"
+      ],
+      "type": "object"
+    },
+    "rating": {
+      "type": "string"
+    },
+    "strengths": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "targetDate": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "person1",
+    "person2",
+    "targetDate",
+    "overallScore",
+    "rating",
+    "cycles",
+    "strengths",
+    "challenges",
+    "advice",
+    "dailySync"
+  ],
+  "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: +[
+  {
+    "person1": {
+      "birthDate": "1990-07-15"
+    },
+    "person2": {
+      "birthDate": "1992-03-22"
+    }
+  }
+]

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.9/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, so the agent knows this is a safe read operation. The description adds some algorithmic detail (overlaying cycle profiles on a target date) but does not disclose additional behavioral traits like authentication needs, rate limits, or edge-case handling. It does not contradict the annotations.

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 a single paragraph that front-loads the core purpose ('Calculate biorhythm compatibility...') and then enumerates outputs and use cases. It is informative without being overly verbose, though it could be improved with bullet points for the long list of outputs.

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?

An output schema exists, so return values are formally covered. The description adds use cases and enumerates the key outputs, making it complete for an agent to decide when to call it. It does not mention any missing prerequisites or edge cases, but given the tool's simplicity, the coverage is adequate.

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 60%, and the schema itself provides descriptions for all parameters (lang, compact, birthDate, targetDate). The tool description does not add any parameter-specific meaning beyond the schema, but given the schema already carries the load, a baseline score of 3 is appropriate.

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 clearly states the verb 'calculate' and the specific resource 'biorhythm compatibility between two people', distinguishing it from sibling tools that focus on single-person or aspect-specific analyses. It lists concrete outputs (physical, emotional, intellectual scores, etc.) making the purpose unambiguous.

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 clear use-case context (dating apps, relationship platforms, team-building, couples coaching) and implies the tool is for two-person compatibility, which differentiates it from siblings. However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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?