Mesoamerican Astrology MCP Server by RoxyAPI

Get one Aztec trecena - Tonalpohualli period profile API

get_mesoamerican_astrology_aztec_trecenas_number

Read-only

Retrieve one of the twenty tonalpohualli trecenas by number, with the day sign it opens on and a composed reading of the period. Built for period detail pages and for apps that show which thirteen day block a date falls in.

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
`number`	Yes	Trecena number, 1 to 20. Trecena 1 opens on 1 Cipactli, trecena 2 on 1 Ocelotl, and each subsequent period opens thirteen signs further round the twenty.
`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
`length`	Yes
`number`	Yes
`reading`	Yes
`startSign`	Yes
`startSignName`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "length": {
+      "type": "number"
+    },
+    "number": {
+      "type": "number"
+    },
+    "reading": {
+      "type": "string"
+    },
+    "startSign": {
+      "type": "string"
+    },
+    "startSignName": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "number",
+    "startSign",
+    "startSignName",
+    "length",
+    "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 establish readOnlyHint and non-destructive safety, so the description only needs to add context. It adds that the result includes the opening day sign and a composed reading, but it does not disclose behavior such as invalid-number handling or the nature of the composed reading; acceptable but not rich.

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 operational core ('retrieve one trecena by number') first and the audience/use case second. Every clause 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?

With a full input schema, an output schema, and read-only annotations, nothing essential is missing. The description supplies the use case and resource scope needed to select the tool correctly, and all behaviors are sufficiently covered by the structured fields.

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 schema carries the meaning of number, lang, and compact. The description's 'by number' and 'twenty' reinforce the number parameter but add no detail beyond what the input schema already provides.

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 uses a specific verb ('Retrieve') plus a precise resource ('one of the twenty tonalpohualli trecenas by number') and states what the caller gets: the opening day sign and a composed reading of the period. This is clearly distinct from the plural list sibling and from the Aztec daily tool.

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?

'Built for period detail pages and for apps that show which thirteen day block a date falls in' gives clear intended contexts. It does not explicitly name an alternative tool or state when not to use it, so it stops short of full when/when-not guidance.

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?