Mesoamerican Astrology MCP Server by RoxyAPI

List the 19 Haab periods - Maya solar calendar month API

get_mesoamerican_astrology_mayan_haab_months

Read-only

Retrieve all nineteen periods of the Haab, the 365 day Maya year: eighteen months of twenty days plus the five days of Wayebʼ. Each entry returns the machine id, both spellings of the name, the length, what the name means and a composed reading. Built for calendar reference pages and for any app that has to label a Haab date rather than only compute it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Response 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
`limit`	No	Maximum items to return per page. Range: 1-19, default 19.
`offset`	No	Number of items to skip for pagination. Default 0.
`compact`	No	Set 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

Name	Required	Description	Default
`limit`	Yes
`total`	Yes
`months`	Yes
`offset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
Changed3 schema fields changedSep 20, 2026
- removedInput schema / properties / offset / default
```
Removed value: -0
```
- removedInput schema / properties / offset / minimum
```
Removed value: -0
```
- changedInput schema / properties / offset / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "limit": {
+      "type": "number"
+    },
+    "months": {
+      "items": {
+        "properties": {
+          "gloss": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "length": {
+            "type": "number"
+          },
+          "nameClassic": {
+            "type": "string"
+          },
+          "nameYucatec": {
+            "type": "string"
+          },
+          "position": {
+            "type": "number"
+          },
+          "reading": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "position",
+          "id",
+          "nameYucatec",
+          "nameClassic",
+          "length",
+          "gloss",
+          "reading"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "limit",
+    "offset",
+    "months"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

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, so the safety profile is covered. The description adds useful behavioral detail beyond annotations: each entry includes 'the machine id, both spellings of the name, the length, what the name means and a composed reading'. This gives the agent a good sense of the response shape without contradicting 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 three sentences with zero filler. The first sentence defines scope, the second explains return content, and the third gives context for use. Every sentence earns its place, and the key information is front-loaded.

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?

The tool has a full output schema, complete parameter descriptions in the schema, and annotations covering the safety profile. The description adds what is not otherwise available: the purpose, the exact set of periods, the return fields, and the intended use case. Nothing needed to select and call this tool correctly 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%, so the input schema already documents all four parameters (lang, limit, offset, compact) with defaults, ranges, and behavior. The description adds no parameter-level semantics beyond what the schema provides, 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 specific verb and resource: 'Retrieve all nineteen periods of the Haab', and adds exact structural detail (eighteen months of twenty days plus the five days of Wayebʼ). It clearly distinguishes this list endpoint from the compute-oriented siblings by framing it as for 'label a Haab date rather than only compute it'.

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: 'calendar reference pages and for any app that has to label a Haab date'. It also implies contrast with computational endpoints ('rather than only compute it'), providing clear context. It stops short of naming sibling alternatives or stating when not to use it, so it loses one point.

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 tools Inspect

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

Need Help?