Skip to main content
Glama

Mesoamerican Astrology MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

Monthly Tzolkin calendar grid - Maya calendar month API

get_mesoamerican_astrology_mayan_calendar_monthly
Read-only

Mayan calendar grid for a whole civil month: every day of the month with its Tzolkin day sign and coefficient, its trecena, its Haab date and its Long Count. One call fills a monthly grid that would otherwise take a request per day, and the answer is fixed for any month that has already begun. Built for calendar widgets, editorial planners and any app that shows a month of Maya dates at once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
yearNoGregorian year of the grid, 1900 to 2100. Defaults to the current year in UTC. Wider historical ranges are available on the single date routes, which are not bounded to this window.
monthNoCalendar month of the grid, 1 to 12. Defaults to the current month in UTC.
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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysYes
yearYes
monthYes
totalYes
conventionsYes

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"
+    },
+    "days": {
+      "items": {
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "daySign": {
+            "type": "string"
+          },
+          "daySignName": {
+            "type": "string"
+          },
+          "haab": {
+            "type": "string"
+          },
+          "longCount": {
+            "type": "string"
+          },
+          "number": {
+            "type": "number"
+          },
+          "trecena": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "date",
+          "daySign",
+          "daySignName",
+          "number",
+          "trecena",
+          "haab",
+          "longCount"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "month": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    },
+    "year": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "year",
+    "month",
+    "total",
+    "days",
+    "conventions"
+  ],
+  "type": "object"
+}
  2. Changed4 schema fields changed
    • addedInput schema / properties / month / maximum
      Added value: +12
    • addedInput schema / properties / month / minimum
      Added value: +1
    • addedInput schema / properties / year / maximum
      Added value: +2100
    • addedInput schema / properties / year / minimum
      Added value: +1900
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful behavioral context beyond that: the response is deterministic ('fixed') for months that have begun, and the endpoint aggregates month-wide data in one call, avoiding per-day requests.

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 with no filler: the first states exactly what the tool returns, the second explains the efficiency benefit, and the third identifies the audience. Key details are front-loaded and 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?

Given that all five optional parameters are fully documented in the schema, annotations cover safety, and an output schema exists, the description completes the picture by explaining the data content, the use case, and why the endpoint exists. Nothing necessary for correct invocation is missing.

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 every parameter already has a detailed description, including defaults, ranges, enums, and behavior. The tool description itself does not need to repeat parameter semantics, so the baseline of 3 applies.

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 precise verb-resource pair: a monthly Maya calendar grid covering every day of a civil month. It enumerates the included data fields (Tzolkin sign and coefficient, trecena, Haab date, Long Count), making the tool's scope unmistakable and distinguishing it from the daily and single-date sibling routes.

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 explicitly says one call fills a whole monthly grid 'that would otherwise take a request per day,' giving clear context for when to choose this over daily endpoints. It also names target use cases (calendar widgets, editorial planners, apps showing a month of Maya dates). It does not explicitly name sibling alternatives, but the guidance is sufficient for selection.

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