Skip to main content
Glama

Mesoamerican Astrology MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

Aztec day sign for a date - Tonalpohualli calculator API

post_mesoamerican_astrology_aztec_tonalpohualli
Read-only

Aztec calendar day sign calculator: returns the tonalpohualli day sign, its coefficient 1 to 13 and its trecena for any Gregorian date, with a composed reading. The count is anchored on the recorded day of the fall of Tenochtitlan and runs in step with the Maya count under the default constant, verified on the anchor and on two modern dates. Built for Aztec calendar apps, Mexica day sign features and AI agents answering what is my Aztec sign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate 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.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
glossYes
scopeYes
numberYes
daySignYes
keynoteYes
trecenaYes
guidanceYes
directionYes
conventionsYes
daySignNameYes

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"
+    },
+    "daySignName": {
+      "type": "string"
+    },
+    "direction": {
+      "type": "string"
+    },
+    "gloss": {
+      "type": "string"
+    },
+    "guidance": {
+      "type": "string"
+    },
+    "keynote": {
+      "type": "string"
+    },
+    "number": {
+      "type": "number"
+    },
+    "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",
+    "conventions"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes safety, and the description adds meaningful behavioral context: the count is anchored on the fall of Tenochtitlan, runs in step with the Maya count under a default constant, and is verified on anchor and modern dates. No contradiction with annotations exists.

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?

The description is three focused sentences with no filler. The first sentence front-loads the core output, the second adds calibration provenance, and the third states use cases. 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 a rich output schema present, the description does not need to enumerate return fields. It covers purpose, calibration basis, verification, and intended use cases, and the schema handles input constraints. The definition is complete for an agent to select and call the tool 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 input schema already documents the date format, proleptic Gregorian convention, lang fallback, and compact shape. The description does not add parameter-level semantics beyond mentioning 'any Gregorian date', so the baseline 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 uses a specific verb-resource pair: 'returns the tonalpohualli day sign, its coefficient 1 to 13 and its trecena for any Gregorian date'. It clearly identifies the tool as a date-based calculator and distinguishes it from the sibling day-sign list and daily-calendar tools by emphasizing the date input and composed reading.

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 context: this is the tool for answering 'what is my Aztec sign' and for Aztec calendar app features. It does not explicitly name exclusions or alternatives, but the date-scoped calculator framing makes the intended use evident against the sibling catalogue/list tools.

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