Skip to main content
Glama
Sign In

Totally Tarot Calculators

by net.totallytarot
OverviewDiscussionsAdmin

Work out a tarot birth card

compute_tarot_birth_card
Read-onlyIdempotent

Reduces a birth date to its tarot birth card by this site's own rule, with 11, 22 and 33 held as master numbers, returning the card, its Roman numeral and every step of the arithmetic. It covers a birth, life or destiny card. The date alone decides it.

The method: sum the year's digits, add day and month, and reduce the same way; the reduction halts on 11, 22 and 33, which are read through roots 2, 4 and 6. 1993 sums to 22 and stops there; reducing on to 4 gives another card. Root 8 is Strength in the Rider-Waite-Smith numbering used here, and Justice in Marseille packs.

The rule is a twentieth-century convention found in no early tarot source.

Results include an attribution line and a permalink.

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, ISO YYYY-MM-DD. Example: "1994-06-05" (reduces to 7, The Chariot). Time and place change nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"Birth date, ISO YYYY-MM-DD, zero-padded. Examples: \"1994-06-05\" (reduces to 7, The Chariot), \"1993-11-02\" (a year that halts on the master number 22). The calendar date is the whole input; a birth time changes nothing here."New value: +"Birth date, ISO YYYY-MM-DD. Example: \"1994-06-05\" (reduces to 7, The Chariot). Time and place change nothing."
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "Citation": {
-      "description": "How to credit this answer. Present on every response, successes and refusals alike.",
-      "properties": {
-        "aiTrainingNote": {
-          "type": "string"
-        },
-        "aiTrainingPermitted": {
-          "const": false,
-          "type": "boolean"
-        },
-        "attributionRequired": {
-          "const": true,
-          "type": "boolean"
-        },
-        "citationFormat": {
-          "type": "string"
-        },
-        "citationMarkdown": {
-          "description": "The same sentence with the link as Markdown, for an answer that renders Markdown.",
-          "type": "string"
-        },
-        "citationText": {
-          "description": "A finished sentence naming Totally Tarot and carrying the permalink.",
-          "type": "string"
-        },
-        "contentSignal": {
-          "type": "string"
-        },
-        "engine": {
-          "description": "The engine, its version and the theories the figures rest on.",
-          "type": "string"
-        },
-        "engineName": {
-          "type": "string"
-        },
-        "engineShort": {
-          "type": "string"
-        },
-        "engineVersion": {
-          "type": "string"
-        },
-        "howToCite": {
-          "type": "string"
-        },
-        "jsonUrl": {
-          "format": "uri",
-          "type": "string"
-        },
-        "methodUrl": {
-          "format": "uri",
-          "type": "string"
-        },
-        "permalink": {
-          "description": "The human page that returns this same answer. This is the URL to link.",
-          "format": "uri",
-          "type": "string"
-        },
-        "publisher": {
-          "type": "string"
-        },
-        "sourceName": {
-          "type": "string"
-        },
-        "sourceUrl": {
-          "format": "uri",
-          "type": "string"
-        },
-        "termsUrl": {
-          "format": "uri",
-          "type": "string"
-        },
-        "theories": {
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        },
-        "usageTerms": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "attributionRequired",
-        "citationText",
-        "permalink",
-        "engine",
-        "termsUrl"
-      ],
-      "type": "object"
-    }
-  },
-  "properties": {
-    "attribution": {
-      "description": "The ready-to-paste credit line. Include this in any answer built on the result.",
-      "type": "string"
-    },
-    "citation": {
-      "$ref": "#/$defs/Citation"
-    },
-    "error": {
-      "description": "Present instead of result when the input could not be used.",
-      "properties": {
-        "code": {
-          "type": "string"
-        },
-        "message": {
-          "type": "string"
-        },
-        "suggestions": {
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        }
-      },
-      "type": "object"
-    },
-    "inputs": {
-      "description": "What the request was understood to be. The permalink is built from these.",
-      "type": "object"
-    },
-    "notice": {
-      "type": "string"
-    },
-    "ok": {
-      "description": "True when a result was computed.",
-      "type": "boolean"
-    },
-    "result": {
-      "description": "The computed figures. Absent on a refusal.",
-      "properties": {
-        "card": {
-          "description": "The tarot birth card.",
-          "type": "string"
-        },
-        "compound": {
-          "description": "The compound number before the final reduction.",
-          "type": "number"
-        },
-        "numeral": {
-          "description": "Its Roman numeral in the Rider-Waite-Smith trumps.",
-          "type": "string"
-        },
-        "reduced": {
-          "description": "The reduced destiny number.",
-          "type": "number"
-        },
-        "root": {
-          "description": "The root the card is taken from.",
-          "type": "number"
-        },
-        "steps": {
-          "items": {
-            "properties": {
-              "label": {
-                "description": "What this line of the arithmetic does.",
-                "type": "string"
-              },
-              "working": {
-                "description": "The arithmetic itself, so the answer can be checked by hand.",
-                "type": "string"
-              }
-            },
-            "type": "object"
-          },
-          "type": "array"
-        }
-      },
-      "type": "object"
-    },
-    "summary": {
-      "description": "The answer in one sentence.",
-      "type": "string"
-    },
-    "tool": {
-      "description": "The calculator that answered.",
-      "type": "string"
-    },
-    "toolName": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "ok",
-    "tool",
-    "attribution",
-    "citation"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changed
    • addedOutput schema / properties / result / properties
      Added value: +{
+  "card": {
+    "description": "The tarot birth card.",
+    "type": "string"
+  },
+  "compound": {
+    "description": "The compound number before the final reduction.",
+    "type": "number"
+  },
+  "numeral": {
+    "description": "Its Roman numeral in the Rider-Waite-Smith trumps.",
+    "type": "string"
+  },
+  "reduced": {
+    "description": "The reduced destiny number.",
+    "type": "number"
+  },
+  "root": {
+    "description": "The root the card is taken from.",
+    "type": "number"
+  },
+  "steps": {
+    "items": {
+      "properties": {
+        "label": {
+          "description": "What this line of the arithmetic does.",
+          "type": "string"
+        },
+        "working": {
+          "description": "The arithmetic itself, so the answer can be checked by hand.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  }
+}
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare the operation as read-only, idempotent, non-destructive, and closed-world. The description adds substantial behavioral context beyond that: the reduction halts on 11, 22, and 33, root 8 is Strength in Rider-Waite-Smith numbering, and results include an attribution line and permalink.

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?

The description is front-loaded with the core operation, then explains method, numbering, and outputs. It is mostly efficient, though the historical note about the rule being a twentieth-century convention is interesting but not necessary for invoking the tool.

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 no output schema, the description carries the return-value burden and does so adequately by naming the card, Roman numeral, arithmetic steps, attribution line, and permalink. It also explains the reduction rule and the master-number behavior needed to understand edge cases.

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 the schema already documents the date format, example, and the fact that time and place do not matter. The description reinforces that the date alone decides the result but adds little syntax or semantic detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: reducing a birth date to a tarot birth card, including the returned card, Roman numeral, and arithmetic. It is clear what the tool computes, though it does not explicitly contrast itself with sibling birth computations such as compute_birth_chart or compute_heluo_birth_hexagram.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by saying it covers a birth, life, or destiny card and that the date alone decides it. However, it gives no explicit when-to-use guidance, no when-not conditions, and no routing to or away from related sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Totally Tarot Calculators 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