Skip to main content
Glama
PattrickChenforclaudeuse

mythsensus-mcp

by PattrickChenforclaudeuse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

calculate_cosmic_score

Read-onlyIdempotent

Calculates a 1-999 Cosmic Score from birth date by synthesizing 26 divination systems, returning score, tier, percentile, and per-system summaries.

Instructions

Compute the Mythsensus Cosmic Score (1-999) for a birth date. Synthesises 26 ancient divination systems including BaZi, Vedic Jyotish, Western astrology, Nine Star Ki, Thai Seven Number, Mayan Tzolk'in, Norse Runes, and 19 others. Returns numeric score, tier (Common→Mythic), percentile, plus a per-system summary (Sun sign, BaZi day master, Vedic nakshatra, Human Design type, etc.). Deterministic: same input always returns the same output. Optionally pass systems[] (typo-tolerant) to focus the preview on specific traditions, and time_known:false when the birth time is unknown. Returns a free 5-of-26 consensus preview; the complete 26-system side-by-side reading is on mythsensus.com.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYesBirth day (1-31)
latNoBirth latitude (optional; default 13.75 = Bangkok)
lonNoBirth longitude (optional; default 100.5 = Bangkok)
hourNoBirth hour (0-23, optional — improves BaZi/Vedic/Western precision; default 12 noon)
langNoOutput language (optional; default th)
yearYesBirth year (4-digit, e.g. 1990)
monthYesBirth month (1-12)
minuteNoBirth minute (0-59, optional; default 0)
systemsNoOptional — limit the consensus preview to specific systems. Free preview covers bazi/vedic/western/ninestar/thai; names are typo-tolerant ("vedik"→vedic, "four pillars"→bazi). Requests beyond the free 5 are noted with an upsell, not returned.
locationNoOptional birthplace — a city name ("Chiang Mai", "เชียงใหม่", "Tokyo") or "lat,lon". Typo-tolerant, resolved offline to coordinates + timezone (no network). Explicit lat/lon/timezone override it.
timezoneNoTimezone offset hours (optional; default +7)
time_knownNoSet false when birth time is unknown — time-dependent layers (BaZi hour pillar, Ascendant/houses) are then flagged approximate. Default: inferred from whether hour is provided.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world. The description adds value beyond that: deterministic output guarantee, the free-tier ceiling where extra systems are 'noted with an upsell, not returned', and inference rules for defaults (time_known, noon/timezone fallbacks). Return contents are also disclosed, which annotations do not cover.

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?

Front-loaded with the core purpose, score range, and output shape, then narrows to optional parameters and the free/paid boundary. Dense but each sentence carries information; no filler.

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 12 parameters, no output schema, and a computation-heavy tool, the description supplies the return shape (score, tier, percentile, per-system summary), the determinant nature, and the free-tier constraint. Nothing essential for a correct call 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 every parameter is already documented in the schema. The description restates key behaviors (typo-tolerant systems, time_known inference) that the schema independently describes, adding confirmation rather than new semantics. Baseline 3 applies when the schema carries the load.

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 with scope ('Compute the Mythsensus Cosmic Score (1-999) for a birth date') and quantifies breadth (26 systems, named examples). An agent can distinguish this from get_deep_reading or list_26_systems from the description alone.

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?

Explains when to pass systems[] and time_known:false, and clarifies the free 5-of-26 preview versus the paid full reading on the website. It does not explicitly say when this tool should be preferred over siblings like get_deep_reading, so it stops short of full alternative-routing guidance.

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

Deploy Server

Other Tools