Skip to main content
Glama

ERUX Astrology & Ephemeris Engine

get_horoscope

Read-onlyIdempotent

Generate a personalized transit horoscope, real-world strategic forecast, and exact astronomical time-windows for a user based on their natal placements and active planetary transits. Corresponds to /horoscope and /daily commands. Supports cadences: 'daily' (today's transits and hourly Horas), 'weekly' (7-day Monday–Sunday transit arc), 'monthly' (30-day sign ingresses & lunations), and 'yearly' (12-month Solar Return to Solar Return Varshaphala journey). MANDATORY PARAMETERS: The user's natal birth date ('birth_date', YYYY-MM-DD) and natal birth city ('birth_city') are strictly required. NEVER pass today's date into 'birth_date' — today's transit date is calculated automatically by the server based on location coordinates. If the user asks for a future or target date (e.g. next week or 2027), pass that date into 'target_date', NOT 'birth_date'. Optionally accepts 'current_city' if the user has relocated, and 'cadence' ('daily', 'weekly', 'monthly', 'yearly'). For daily cadence, returns 'astronomical_time_windows' (exact topocentric sunrise/sunset, 24 planetary Horas, Rahu Kaal, Abhijit Muhurta, Brahma Muhurta) and 'panchang_timing' (exact Nakshatra and Tithi transitions). CRITICAL FOR AI: When suggesting times of day, you MUST quote the exact astronomical_time_windows provided. Never invent arbitrary hours.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_horoscope"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoAlias for natal birth city
dateNoAlias for natal birth date (YYYY-MM-DD)
timeNoAlias for natal birth time (HH:MM)
cadenceNoForecast time window: 'daily' (Horas & Panchang), 'weekly' (7-day), 'monthly' (30-day), or 'yearly' (Varshaphala)daily
countryNoCountry of birth or current location
birth_cityNoREQUIRED: User's natal birth city (e.g. 'London', 'Austin', 'Mumbai').
birth_dateNoREQUIRED: User's natal birth date (YYYY-MM-DD, e.g. '1990-07-12'). Do NOT pass today's date here.
birth_timeNoNatal birth time in 24-hour HH:MM format (default '12:00' if unknown)12:00
target_cityNoAlias for current relocated city
target_dateNoTarget forecast date in YYYY-MM-DD format (must be today or future date)
current_cityNoCurrent relocated city for topocentric horizon and local Horas (e.g. 'London')
birth_countryNoNatal country to disambiguate birth city
include_imageNoSet to true to render and attach a dynamic chart wheel PNG image buffer in MCP outputs (default false)
current_countryNoCurrent relocated country

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / user_prompt
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "User's original inquiry for intent grounding and conversational context",
      -  "title": "User Prompt"
      -}
  2. Changed16 schema fields changed
    • addedInput schema / properties / birth_city / description
      Added value: +"REQUIRED: User's natal birth city (e.g. 'London', 'Austin', 'Mumbai')."
    • addedInput schema / properties / birth_country / description
      Added value: +"Natal country to disambiguate birth city"
    • addedInput schema / properties / birth_date / description
      Added value: +"REQUIRED: User's natal birth date (YYYY-MM-DD, e.g. '1990-07-12'). Do NOT pass today's date here."
    • addedInput schema / properties / birth_time / description
      Added value: +"Natal birth time in 24-hour HH:MM format (default '12:00' if unknown)"
    • addedInput schema / properties / cadence / description
      Added value: +"Forecast time window: 'daily' (Horas & Panchang), 'weekly' (7-day), 'monthly' (30-day), or 'yearly' (Varshaphala)"
    • addedInput schema / properties / city / description
      Added value: +"Alias for natal birth city"
    • addedInput schema / properties / country / description
      Added value: +"Country of birth or current location"
    • addedInput schema / properties / current_city / description
      Added value: +"Current relocated city for topocentric horizon and local Horas (e.g. 'London')"
    • addedInput schema / properties / current_country / description
      Added value: +"Current relocated country"
    • addedInput schema / properties / date / description
      Added value: +"Alias for natal birth date (YYYY-MM-DD)"
    • addedInput schema / properties / include_image
      Added value: +{
      +  "default": false,
      +  "description": "Set to true to render and attach a dynamic chart wheel PNG image buffer in MCP outputs (default false)",
      +  "title": "Include Image",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / target_city / description
      Added value: +"Alias for current relocated city"
    • addedInput schema / properties / target_date / description
      Added value: +"Target forecast date in YYYY-MM-DD format (must be today or future date)"
    • addedInput schema / properties / time / description
      Added value: +"Alias for natal birth time (HH:MM)"
    • addedInput schema / properties / user_prompt / description
      Added value: +"User's original inquiry for intent grounding and conversational context"
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "additionalProperties": true,
      -      "title": "Result",
      -      "type": "object"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "get_horoscopeOutput",
      -  "type": "object"
      -}New value: +null
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description goes further by disclosing server-side behavior: today's transit date is computed automatically from location coordinates, and daily cadence returns astronomical_time_windows plus panchang_timing. The instruction to quote exact windows rather than invent hours is genuinely useful behavioral context. It does not cover rate limits, error modes, or what happens with missing birth data.

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

Conciseness3/5

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

The opening sentence is well front-loaded, but the body is dense with all-caps warnings, repeated parenthetical enumerations, and an opaque reference to '/horoscope and /daily commands' that means nothing to an agent. The mandatory-parameter warning is restated in both the prose and the parameter list, so some content is redundant. It still parses into purpose → params → returns → caveat, so structure is reasonable.

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 14-parameter tool with no output schema, the description does the necessary work: it defines which inputs are mandatory, how dates are interpreted, and what daily returns look like. Gaps remain — return content for weekly/monthly/yearly cadences is described only as an arc or journey with no output fields, and include_image is never mentioned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning: it designates birth_date/birth_city as mandatory (the schema marks zero required fields, so this compensates for a genuine schema gap) and explains the birth_date vs target_date distinction with a rationale. It leaves several parameters untouched, notably include_image and the alias set (city/date/time/target_city), which are only documented in 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?

States a specific verb and multi-part resource: a personalized transit horoscope, strategic forecast, and exact astronomical time-windows derived from natal placements plus active transits, then enumerates the four cadences. The transit/forecast framing implicitly distinguishes it from natal-chart siblings like calculate_chart, but no sibling is named explicitly, so differentiation is left to inference.

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?

Clear guidance on parameter routing: 'NEVER pass today's date into birth_date' and 'If the user asks for a future or target date ... pass that date into target_date'. It also explains when current_city matters (relocated user) and enumerates the cadence options. It stops short of explicitly contrasting this tool with ask_astrology_guidance or get_interpretation, so the when-to-use-this-vs-that is incomplete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.