Skip to main content
Glama

Mesoamerican Astrology MCP Server by RoxyAPI

by com.roxyapi

Mayan day sign for a date - Tzolkin calculator API

post_mesoamerican_astrology_mayan_tzolkin
Read-only

Mayan astrology day sign calculator: returns the Tzolkin day sign, the coefficient 1 to 13 and the trecena for any Gregorian date, under the correlation living daykeepers use, with a composed nawal reading. Built for Mayan zodiac apps, daily energy feeds and AI agents answering what is my Mayan sign. Classical Maya count only, with the correlation echoed on every response so a saved reading stays reproducible.

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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only and non-destructive behavior. The description adds useful behavioral context beyond that: it states that the correlation is 'echoed on every response so a saved reading stays reproducible,' and constrains the scope to 'Classical Maya count only.' These are meaningful behavioral guarantees not present in 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded, with the core purpose stated in the first clause. Every sentence earns its place: the first defines the output, the second names use cases, and the third adds a reproducibility guarantee. There is no filler or repetition.

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 no output schema, the description appropriately names the key return values: day sign, coefficient, trecena, nawal reading, and echoed correlation. Parameter responsibilities are fully covered by the schema, and the read-only behavior is already annotated, so an agent has enough context to select and invoke 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 baseline is 3. The description reinforces that the date drives the calculation and that the default correlation is the one 'living daykeepers use,' but it does not add substantial parameter-level meaning beyond the already thorough schema descriptions for date, lang, compact, and correlation.

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 opens with a specific verb and resource: 'returns the Tzolkin day sign, the coefficient 1 to 13 and the trecena for any Gregorian date.' It also names concrete outputs (nawal reading, correlation echo) and clearly exists for a distinct task — computing a Mayan day sign for a date — which separates it from sibling sign-listing and daily-feed tools.

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 application contexts: 'Built for Mayan zodiac apps, daily energy feeds and AI agents answering what is my Mayan sign.' This tells an agent when the tool is useful, though it does not explicitly name sibling alternatives or state when not to use this tool in favor of another.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation3/5

Most tools are cleanly separated by tradition and resource type, but the Aztec and Mayan 'daily' endpoints overlap heavily with the corresponding tonalpohualli/tzolkin calculators: both return the day sign, coefficient, trecena, and a reading for a date. The descriptions hint at different use cases, but an agent could easily select the wrong one for a daily feed or sign lookup.

Naming Consistency5/5

All tools follow the same lowercase snake_case convention: get_/post_ + mesoamerican_astrology + aztec/mayan + resource + optional selector. GET is consistently used for fixed/reference content and POST for computation, making the hierarchy predictable across every endpoint.

Tool Count4/5

18 tools is slightly high but reasonable for covering two calendar traditions with list/detail endpoints for signs, trecenas, and Mayan Haab months. The duplicate daily/calculator pairs inflate the count somewhat, but the overall surface is not bloated for the stated purpose.

Completeness4/5

The server thoroughly covers Mayan Tzolkin, Haab, Long Count, charts, and compatibility, plus Aztec tonalpohualli signs, trecenas, and date conversion. Notable gaps are the absence of an Aztec 365-day Xiuhpohualli/monthly calendar and Aztec chart/compatibility endpoints, but core lookups and readings are well covered.

Resources