Mesoamerican Astrology MCP Server by RoxyAPI

Get one Haab period - Maya solar calendar month profile API

get_mesoamerican_astrology_mayan_haab_months_id

Read-only

Retrieve one of the nineteen Haab periods by id, with both spellings of its name, its position in the year, its length and a composed reading. Built for calendar detail pages and for labelling a Haab date a chart route has already returned.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Haab period id, case-insensitive and punctuation-insensitive. One of pop, wo, sip, sotz, sek, xul, yaxkin, mol, chen, yax, sak, keh, mak, kankin, muwan, pax, kayab, kumku, wayeb.
`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
`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
`id`	Yes
`gloss`	Yes
`length`	Yes
`reading`	Yes
`position`	Yes
`nameClassic`	Yes
`nameYucatec`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+}

First observedSep 6, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so no safety disclosure is needed. The description adds the return-payload scope (spellings, position, length, composed reading) but little behavioral context beyond that; it is a straightforward read operation.

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?

Two sentences, no filler, with the primary action and returned data front-loaded. The second sentence adds concrete use-case context without repeating schema or annotation information.

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?

For a single-record read tool with full schema coverage, an output schema, and safety annotations, this description is complete. It tells the agent what the tool returns, when to use it, and where it fits in the workflow.

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%, with enums and clear descriptions for id, lang, and compact. The description does not need to add parameter-level guidance, and the baseline of 3 applies because the schema carries the semantic weight.

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 identifies a specific verb ('Retrieve'), a precise resource ('one of the nineteen Haab periods by id'), and enumerates the notable returned fields. It clearly distinguishes this detail/ID tool from the sibling list tool, haab_months, by emphasizing single-record retrieval.

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: calendar detail pages and labelling a Haab date returned by a chart route. It does not explicitly name alternative sibling tools or list when-not-to-use conditions, but the intended context is clear enough for an agent.

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?