Skip to main content
Glama

Mesoamerican Astrology MCP Server by RoxyAPI

by com.roxyapi

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

Schema Changelog

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

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that content is fixed for a given date, rolls over at midnight UTC, and is safe to cache and pre-fill weeks ahead. These are useful behavioral guarantees that materially affect how an agent can schedule and cache calls.

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, each earning its place: the first defines the deliverable, the second gives deterministic caching behavior, and the third states target use cases. The core value is front-loaded and there is no redundant filler.

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?

With no output schema, the description still names the key returned components: day sign, coefficient, trecena, and composed reading. Combined with the rich parameter schema and strong behavioral context, this is nearly complete, though an explicit response-shape hint would make it fully self-sufficient.

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 detailed semantics for date, lang, compact, and correlation. The description adds only a minor supporting note that any date can be named, so it meets the baseline but does not meaningfully go beyond the schema.

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 states a specific verb-resource combination: it returns the Tzolkin day sign, its coefficient, and its trecena for today or a named date, with a composed reading. This clearly distinguishes it from sibling reference tools like mayan_day_signs, mayan_trecenas, and calendar_monthly, while the Mayan-vs-Aztec framing separates it from the aztec_daily 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?

The description gives explicit use cases: daily energy widgets, nawal of the day feeds, and chatbot answers about what today carries. It does not explicitly name sibling tools or state when not to use this tool, but the intended context is clear enough for an agent to route appropriately.

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