Skip to main content
Glama

Mesoamerican Astrology MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

List the 20 Mayan day signs - Tzolkin nawal catalogue API

get_mesoamerican_astrology_mayan_day_signs
Read-only

Retrieve all twenty Tzolkin day signs in sequence order from Imix to Ajaw. Each entry returns the machine id, the name in the standard orthography, the sixteenth century spelling and the Kʼicheʼ name from the living daykeeping tradition, both published glosses, and the world direction and colour under the requested scheme. Built for nawal pickers, sign reference pages and any app that needs the whole set in one call.

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
limitNoMaximum items to return per page. Range: 1-20, default 20.
offsetNoNumber of items to skip for pagination. Default 0.
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.
directionSchemeNoWhich reading of the world direction and colour to serve for a day sign. The two published assignments differ by exactly one quarter turn on all twenty signs, so neither is a rounding of the other and a silent pick would be a school choice. "madrid-codex" is the codex reading and the default; "landa" is the sixteenth century assignment recorded beside it.madrid-codex

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitYes
totalYes
offsetYes
daySignsYes
conventionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / offset / default
      Added value: +0
    • addedInput schema / properties / offset / minimum
      Added value: +0
  2. Changed3 schema fields changed
    • 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"
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "conventions": {
+      "properties": {
+        "directionScheme": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "directionScheme"
+      ],
+      "type": "object"
+    },
+    "daySigns": {
+      "items": {
+        "properties": {
+          "color": {
+            "type": "string"
+          },
+          "direction": {
+            "type": "string"
+          },
+          "gloss": {
+            "type": "string"
+          },
+          "glossAlternate": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "nameClassic": {
+            "type": "string"
+          },
+          "nameKiche": {
+            "type": "string"
+          },
+          "nameYucatec": {
+            "type": "string"
+          },
+          "position": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "position",
+          "id",
+          "nameYucatec",
+          "nameClassic",
+          "nameKiche",
+          "gloss",
+          "glossAlternate",
+          "direction",
+          "color"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "limit",
+    "offset",
+    "daySigns",
+    "conventions"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.2/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. The description adds meaningful behavioral context: sequence ordering, the full set of fields returned per entry, and the directionScheme-dependent direction and colour. This goes beyond the annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three purposeful sentences: the first states the core action, the second enumerates returned fields, and the third gives use cases. The field list is dense but informative, and no sentence is wasted.

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 the rich input schema, output schema, and safe-read annotations, the description is complete enough for an agent to select and invoke the tool correctly. It explains the tool's scope, return contents, ordering, and target use cases without needing to duplicate structured schema details.

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 has a detailed schema description. The tool description does not need to restate parameter semantics; it only lightly references the 'requested scheme' for directionScheme. Baseline 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?

States a specific verb and resource: 'Retrieve all twenty Tzolkin day signs in sequence order from Imix to Ajaw.' It also distinguishes itself from the sibling mayan_day_signs_id tool by emphasizing the whole set in one call and positioning itself as the catalogue endpoint.

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 usage context: 'Built for nawal pickers, sign reference pages and any app that needs the whole set in one call.' It does not explicitly name alternatives or exclusions, but the whole-set framing implicitly routes agents away from the single-id sibling.

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