Skip to main content
Glama

Mesoamerican Astrology MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

Daily Mayan energy reading - Tzolkin day sign of the day API

get_mesoamerican_astrology_mayan_daily
Read-only

Mayan energy of the day: the Tzolkin day sign, its coefficient and its trecena for today or for any date you name, with a composed reading. Content is fixed for a given date and rolls over at midnight UTC, so a daily feed can cache it safely and an editorial calendar can be filled weeks ahead. Built for daily energy widgets, nawal of the day feeds and chatbot answers about what today carries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded. Defaults to the current day in UTC.
langNoResponse 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
compactNoSet 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.
correlationNoWhich correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. "gmt-584283" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. "martinez-hernandez-584281" sits two days earlier, "astronomical-584285" two days later, and "martin-skidmore-584286" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.gmt-584283

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
numberYes
daySignYes
readingYes
trecenaYes
overviewYes
conventionsYes
daySignNameYes
daySignKicheYes
daySignClassicYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "conventions": {
+      "properties": {
+        "correlation": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "correlation"
+      ],
+      "type": "object"
+    },
+    "date": {
+      "type": "string"
+    },
+    "daySign": {
+      "type": "string"
+    },
+    "daySignClassic": {
+      "type": "string"
+    },
+    "daySignKiche": {
+      "type": "string"
+    },
+    "daySignName": {
+      "type": "string"
+    },
+    "number": {
+      "type": "number"
+    },
+    "overview": {
+      "type": "string"
+    },
+    "reading": {
+      "properties": {
+        "challenges": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "guidance": {
+          "type": "string"
+        },
+        "keynote": {
+          "type": "string"
+        },
+        "numberBand": {
+          "type": "string"
+        },
+        "numberReading": {
+          "type": "string"
+        },
+        "strengths": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "keynote",
+        "numberReading",
+        "strengths",
+        "challenges",
+        "guidance"
+      ],
+      "type": "object"
+    },
+    "trecena": {
+      "properties": {
+        "dayOfTrecena": {
+          "type": "number"
+        },
+        "number": {
+          "type": "number"
+        },
+        "rulingSign": {
+          "type": "string"
+        },
+        "rulingSignName": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "number",
+        "dayOfTrecena",
+        "rulingSign",
+        "rulingSignName"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "daySign",
+    "daySignName",
+    "daySignClassic",
+    "daySignKiche",
+    "number",
+    "trecena",
+    "date",
+    "overview",
+    "reading",
+    "conventions"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=falseependently. The description adds valuable behavioral context beyond those annotations: content is fixed per date, rolls over at midnight UTC, is cache-safe, and can be precomputed weeks ahead. This meaningfully helps an agent decide how to call and cache the tool.

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 sentences with no filler: the first states the core functionality, the second adds a critical caching/rollover behavior, and the third names the intended use cases. The description is front-loaded and 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?

Combined with a 100%-covered input schema, rich enum documentation, an output schema, and read-only annotations, the description leaves nothing essential unexplained. A caller can select the tool for a daily-reading use case)Skip knowing all parameters from the schema and expect deterministic, cacheable content.

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%, and the schema already provides exhaustive detail on date, lang, compact, and correlation. The description indirectly touches date semantics ('for today or any date', 'midnight UTC') but adds no parameter-level information beyond what the input schema already documents.

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 identifies the resource: 'the Tzolkin day sign, its coefficient and its trecena for today or for any date you name, with a composed reading.' It distinguishes itself from sibling list/reference tools by focusing on the daily energy reading rather than a catalog of signs, though it does not explicitly name any sibling.

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?

It gives clear context for when to use this tool with 'Built for daily energy widgets, nawal of the day feeds and chatbot answers about what today carries.' It also explains a strong practical property—content is fixed and cached safely, enabling editorial calendars—but it does not state when to prefer an alternative sibling tool.

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

All Mesoamerican Astrology MCP Server by RoxyAPI toolsInspect
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