Skip to main content
Glama
Sign In

GenesisCore Astrology (Western + Vedic)

by io.github.AETHER-CORE1219
OverviewDiscussionsAdmin

Western + Vedic signs for a birth moment

calculate_birth_chart_signs

Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune and Pluto signs in both the Western tropical zodiac and the Vedic sidereal zodiac (Lahiri), Moon nakshatra, retrograde flags, and optional Ascendant/MC/Lagna when latitude and longitude are given. Use for questions like 'what is my moon sign', 'my Vedic rashi', 'my Venus sign'. Returns explanation page links and a link to a full free reading.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>"
    },
    "name": "calculate_birth_chart_signs"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date YYYY-MM-DD (1900-2100)
langNoLanguage of links (default en)
timeNoLocal birth time HH:MM 24h. Defaults to 12:00; the Moon can change sign within a day, so ask for the time.
latitudeNoOptional, birthplace latitude (-66..66) for Ascendant
longitudeNoOptional, birthplace longitude, east positive
utc_offsetNoHours from UTC at the birthplace on that date, e.g. 9 Tokyo, 5.5 India, -3 São Paulo, -5 New York winter / -4 summer, 1 Madrid winter / 2 summer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the return composition (explanation page links plus a link to a free reading) and conditional behavior — Ascendant/MC/Lagna appear only when latitude and longitude are supplied. It is silent on failure modes, latency, or what happens for dates outside the supported range, which leaves a small gap.

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 sentences: output inventory first, then example questions, then return-value summary — front-loaded and free of filler. The opening sentence is a long enumeration, but each item is load-bearing content an agent needs for matching.

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 six-parameter tool with no output schema, the description usefully states what comes back and under what condition the optional angles appear, which is the main thing the schema cannot convey. It does not flag that omitting time degrades Moon-sign accuracy (that caution lives only in the schema) or how invalid inputs behave.

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 all six parameters are already documented, including the latitude-for-Ascendant link. The description restates the lat/long-to-Ascendant dependency and names the Lahiri ayanamsa, adding little beyond what the schema already provides, so the baseline 3 applies.

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 enumerates exactly what is produced — Western tropical and Vedic sidereal (Lahiri) signs for ten bodies, Moon nakshatra, retrograde flags, and optional Ascendant/MC/Lagna — so the resource and scope ('birth moment') are unambiguous. It implicitly separates itself from get_current_sky by anchoring everything to a birth date, but never names a sibling explicitly, which keeps it short of a 5.

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?

Concrete example user questions ('what is my moon sign', 'my Vedic rashi', 'my Venus sign') give a clear trigger context. There are no exclusions or named alternatives telling the agent when NOT to call this versus get_current_sky or get_sign_ingresses.

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

All GenesisCore Astrology (Western + Vedic) 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