Mesoamerican Astrology MCP Server by RoxyAPI

Daily Aztec energy reading - Tonalpohualli day sign of the day API

get_mesoamerican_astrology_aztec_daily

Read-only

Aztec energy of the day: the tonalpohualli 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, Mexica day sign feeds and chatbot answers about what today carries.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Date 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.
`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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes
`gloss`	Yes
`scope`	Yes
`number`	Yes
`daySign`	Yes
`keynote`	Yes
`trecena`	Yes
`guidance`	Yes
`overview`	Yes
`direction`	Yes
`conventions`	Yes
`daySignName`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "conventions": {
+      "properties": {
+        "correlation": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "correlation"
+      ],
+      "type": "object"
+    },
+    "date": {
+      "type": "string"
+    },
+    "daySign": {
+      "type": "string"
+    },
+    "daySignName": {
+      "type": "string"
+    },
+    "direction": {
+      "type": "string"
+    },
+    "gloss": {
+      "type": "string"
+    },
+    "guidance": {
+      "type": "string"
+    },
+    "keynote": {
+      "type": "string"
+    },
+    "number": {
+      "type": "number"
+    },
+    "overview": {
+      "type": "string"
+    },
+    "scope": {
+      "type": "string"
+    },
+    "trecena": {
+      "properties": {
+        "dayOfTrecena": {
+          "type": "number"
+        },
+        "number": {
+          "type": "number"
+        },
+        "startSign": {
+          "type": "string"
+        },
+        "startSignName": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "number",
+        "dayOfTrecena",
+        "startSign",
+        "startSignName"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "daySign",
+    "daySignName",
+    "gloss",
+    "direction",
+    "number",
+    "trecena",
+    "keynote",
+    "guidance",
+    "scope",
+    "date",
+    "overview",
+    "conventions"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already mark the tool read-only and non-destructive, and the description adds meaningful behavioral detail: content is fixed per date, rolls over at midnight UTC, and is safe to cache for daily feeds or pre-fill an editorial calendar. It also discloses the output composition (day sign, coefficient, trecena, composed reading). No contradiction with annotations.

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 short sentences front-load the core output and date flexibility, then add caching behavior and use cases. Every sentence earns its place and there is no filler or redundancy.

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?

Given the rich schema, the presence of an output schema, and the safety-oriented annotations, the description is complete enough for correct invocation and interpretation. It states what the reading contains, date rollover behavior, caching implications, and target integrations, leaving no essential gap.

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?

The input schema already documents all three parameters at 100% coverage, including date format and proleptic Gregorian caveats, lang enum with fallback behavior, and compact shape. The description only echoes 'today or any date you name' without adding parameter-level meaning. Baseline 3 is appropriate because the schema carries the semantic weight.

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 names a concrete resource: the Tonalpohualli day sign, its coefficient, its trecena, and a composed reading for today or any named date. The 'daily' scoping and 'any date you name' clearly distinguish it from the sibling list/detail tools like aztec_day_signs or trecenas. An agent can tell what this tool returns without opening the schema.

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 gives clear intended use contexts: daily energy widgets, Mexica day sign feeds, and chatbot answers about what today carries. It does not explicitly name sibling alternatives or state when not to use this tool, such as when a static reference list of day signs would be more appropriate. Thus it has clear context but no exclusions.

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 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?