Skip to main content
Glama

Mesoamerican Astrology MCP Server by RoxyAPI

Generate a Mayan chart - Tzolkin, Haab and Long Count calculator API

post_mesoamerican_astrology_mayan_chart
Read-only

Mayan astrology birth chart from one date: the Tzolkin day sign and coefficient, the Haab date, the full Long Count with its day count, the Calendar Round, the Lord of the Night, the Year Bearer of the Haab year and the five point Cruz Maya, each with composed readings. Built for nawal readings, birth chart features and multi domain spiritual apps that show a Mayan card beside a natal chart. Every school split in the domain is a typed parameter and comes back echoed, so the chart can be reproduced exactly.

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
yearBearerSystemNoWhich Haab day is read as the start of the year when naming its Year Bearer. Only four of the twenty day signs can ever carry a year, and which four depends entirely on this choice, so the three schools never agree. "classic" reads the seating of Pop and is the default, because it is the set highland daykeepers still use; its four bearers are Ikʼ, Manikʼ, Ebʼ and Kabʼan. "campeche" reads 1 Pop and gives Akʼbʼal, Lamat, Bʼen and Etzʼnabʼ. "colonial-yucatec" reads 2 Pop and gives Kʼan, Muluk, Ix and Kawak. The three sets share no member, so a bearer alone tells you which school produced it.classic

Schema Changelog

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

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The readOnlyHint=true and destructiveHint=false annotations already establish that the call is safe and non-destructive. The description adds useful behavioral context: every school split is a typed parameter and is echoed back in the response so the chart can be reproduced exactly. No contradiction with the annotations is present.

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 three sentences, each with a distinct job: enumerating outputs, stating target use cases, and explaining reproducibility. The first sentence is dense and front-loaded, and there is little waste, though the second sentence is slightly wordy.

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?

For a tool with no output schema, the description lists all major output components and the parameter behavior needed to reproduce a chart. The input schema covers date restrictions, language, compact shape, and correlation constants, so the combined information is sufficient for an agent to invoke it 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?

The input schema covers all 5 parameters at 100% with detailed descriptions, defaults, enums, and examples, so the description does not need to repeat parameter mechanics. The description adds only a high-level note that school splits are typed parameters and echoed, which is helpful but not necessary given the schema depth.

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 specifies the resource: a Mayan astrology birth chart generated from a single date, and enumerates all major computed components: Tzolkin day sign and coefficient, Haab date, Long Count with day count, Calendar Round, Lord of the Night, Year Bearer, and Cruz Maya. This distinguishes it from sibling tools like daily Mayan readings, compatibility, or long-count conversion 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 states concrete use cases: nawal readings, birth chart features, and spiritual apps showing a Mayan card beside a natal chart. It does not explicitly name alternatives or give when-not-to-use conditions, but the one-date birth chart framing and sibling tool names make the intended selection clear.

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

Try in Browser

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