Mesoamerican Astrology MCP Server by RoxyAPI

Get one Aztec day sign - Tonalpohualli sign profile API

get_mesoamerican_astrology_aztec_day_signs_id

Read-only

Retrieve the full profile of one tonalpohualli day sign: the Nahuatl name, what it means, the world direction it belongs to, a composed keynote and one line of guidance. Built for Aztec sign detail pages, day sign cards and chatbot answers about a single Mexica sign.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Day sign id, case-insensitive and punctuation-insensitive. One of cipactli, ehecatl, calli, cuetzpalin, coatl, miquiztli, mazatl, tochtli, atl, itzcuintli, ozomahtli, malinalli, acatl, ocelotl, cuauhtli, cozcacuauhtli, ollin, tecpatl, quiahuitl, xochitl.
`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
`essence`	Yes
`keynote`	Yes
`guidance`	Yes
`position`	Yes
`direction`	Yes
`nameNahuatl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "direction": {
+      "type": "string"
+    },
+    "essence": {
+      "type": "string"
+    },
+    "gloss": {
+      "type": "string"
+    },
+    "guidance": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "keynote": {
+      "type": "string"
+    },
+    "nameNahuatl": {
+      "type": "string"
+    },
+    "position": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "position",
+    "id",
+    "nameNahuatl",
+    "gloss",
+    "direction",
+    "essence",
+    "guidance",
+    "keynote"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the description only adds that the result includes specific profile fields. It does not disclose any edge cases, error behavior, or authorization needs. With annotations covering safety, the description adds moderate value by outlining the return contents but no deeper behavioral context.

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 a single, well-structured sentence that front-loads the core action and content, then adds use cases. Every clause earns its place with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-id lookup with an output schema present, the description adequately conveys the purpose and typical usage. It does not explicitly contrast with the plural list endpoint or the trecenas endpoints, but the name and phrasing are sufficiently clear. Minor gaps include no mention of language behavior (though schema covers it) and no explicit read-only indication (annotations cover it).

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 already documents id (with enum and case-insensitivity), lang (with BCP 47 and fallback behavior), and compact (with token savings). The description adds no parameter-specific meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 clearly states a specific verb ('Retrieve') and resource ('the full profile of one tonalpohualli day sign'), and enumerates the content (Nahuatl name, meaning, direction, keynote, guidance). It also implies singular scope, distinguishing it from the plural sibling get_mesoamerican_astrology_aztec_day_signs without needing to open the schema.

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 mentions 'single Mexica sign' and lists concrete use cases (detail pages, day sign cards, chatbot answers), which implies when to use it. However, it does not explicitly name alternatives or state when not to use it, leaving some inference to the agent despite the clear singular/plural naming convention.

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?