Mesoamerican Astrology MCP Server by RoxyAPI

List the 20 Mayan trecenas - Tzolkin thirteen day period API

get_mesoamerican_astrology_mayan_trecenas

Read-only

Retrieve all twenty trecenas, the thirteen day periods the 260 day Tzolkin divides into. Each entry returns the period number, the day sign it opens on in both naming traditions, and a composed reading of what the period carries. Built for calendar apps, energy period trackers and content planners that work in thirteen day blocks rather than in weeks.

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-20, default 20.
`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
`offset`	Yes
`trecenas`	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"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    },
+    "trecenas": {
+      "items": {
+        "properties": {
+          "length": {
+            "type": "number"
+          },
+          "number": {
+            "type": "number"
+          },
+          "reading": {
+            "type": "string"
+          },
+          "rulingSign": {
+            "type": "string"
+          },
+          "rulingSignKiche": {
+            "type": "string"
+          },
+          "rulingSignName": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "number",
+          "rulingSign",
+          "rulingSignName",
+          "rulingSignKiche",
+          "length",
+          "reading"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "total",
+    "limit",
+    "offset",
+    "trecenas"
+  ],
+  "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, and the description adds behavioral context by stating that it returns all twenty trecenas and what each entry contains. It also notes the composed reading aspect, which is useful beyond the structured schema. It does not cover pagination behavior, but the output schema and parameter documentation fill much of that gap.

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 tightly written sentences: the first states the resource, the second describes the return content, and the third gives usage context. There is no redundant language or repetition of schema details.

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?

With a rich output schema, fully documented parameters, and annotations covering safety, the description completes the picture by explaining the domain, the returned fields, and the intended use. Nothing an agent needs to select or invoke this list endpoint 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 coverage is 100%, so the parameters (lang, limit, offset, compact) are fully documented in the schema itself. The description does not add parameter-level meaning beyond what the input schema provides. A baseline score of 3 is appropriate because the schema carries the burden.

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 begins with 'Retrieve all twenty trecenas,' a specific verb and resource, and clarifies the domain with 'the thirteen day periods the 260 day Tzolkin divides into.' It also lists what each entry contains, making it easy to distinguish this list endpoint from siblings like get_mesoamerican_astrology_mayan_trecenas_number.

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 clear context for when this tool fits: 'Built for calendar apps, energy period trackers and content planners that work in thirteen day blocks rather than in weeks.' It does not explicitly name alternatives or state when not to use it, but the use case is specific enough to guide 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?