ERUX Astrology & Ephemeris Engine

get_interpretation

Read-onlyIdempotent

Get deep personalized astrological interpretation for canonical life pillars or placements (e.g. 'career_and_vocation', 'relationships', 'dasha_analysis', 'wealth_and_finance', 'health_and_vitality'). Corresponds to the /interpret slash command in Discord and Google Chat. Can be run with or without specific birth details.

Input Schema

Name	Required	Description	Default
`city`	No	Optional birth city for natal chart mapping
`date`	No	Optional birth date in YYYY-MM-DD format for personalized placements
`time`	No	Optional birth time in 24-hour HH:MM format (default '12:00')	12:00
`topic`	No	Canonical life pillar: 'career_and_vocation', 'relationships', 'wealth_and_finance', 'health_and_vitality', or 'inner_growth'	career_and_vocation
`system`	No	Astrological coordinate framework: 'hybrid', 'vedic', or 'western'	hybrid
`platform`	No	Caller host platform or MCP client identifier (e.g. 'chatgpt', 'claude_desktop', 'cursor', 'windsurf', 'smithery', 'global_registry', 'zed', or any custom client). Defaults to 'mcp_gateway'	mcp_gateway
`birth_city`	No	Explicit alias for natal birth city
`birth_date`	No	Explicit alias for natal birth date (YYYY-MM-DD)
`target_city`	No	Alias for current relocated city
`user_prompt`	No	Raw user query for intent arbitration
`current_city`	No	Current relocated city
`birth_country`	No	Explicit alias for natal birth country

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 11, 2026

addedInput schema / properties / birth_city / description
```
Added value: +"Explicit alias for natal birth city"
```
addedInput schema / properties / birth_country / description
```
Added value: +"Explicit alias for natal birth country"
```

addedInput schema / properties / birth_date / description

Added value: +"Explicit alias for natal birth date (YYYY-MM-DD)"

addedInput schema / properties / city / description

Added value: +"Optional birth city for natal chart mapping"

addedInput schema / properties / current_city / description
```
Added value: +"Current relocated city"
```

addedInput schema / properties / date / description

Added value: +"Optional birth date in YYYY-MM-DD format for personalized placements"

addedInput schema / properties / platform

Added value: +{
+  "default": "mcp_gateway",
+  "description": "Caller host platform or MCP client identifier (e.g. 'chatgpt', 'claude_desktop', 'cursor', 'windsurf', 'smithery', 'global_registry', 'zed', or any custom client). Defaults to 'mcp_gateway'",
+  "title": "Platform",
+  "type": "string"
+}

addedInput schema / properties / system / description

Added value: +"Astrological coordinate framework: 'hybrid', 'vedic', or 'western'"

addedInput schema / properties / target_city / description
```
Added value: +"Alias for current relocated city"
```

addedInput schema / properties / time / description

Added value: +"Optional birth time in 24-hour HH:MM format (default '12:00')"

addedInput schema / properties / topic / description

Added value: +"Canonical life pillar: 'career_and_vocation', 'relationships', 'wealth_and_finance', 'health_and_vitality', or 'inner_growth'"

addedInput schema / properties / user_prompt / description
```
Added value: +"Raw user query for intent arbitration"
```

First observedOct 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that it works with or without birth details (a behavioral fallback) and ties it to a slash-command equivalent, but says nothing about output shape, latency, or auth expectations.

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 short sentences, front-loaded with the core purpose before examples and the slash-command note. No filler, though the examples list makes the first sentence long.

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?

An output schema exists, so return values need not be explained, and the description covers purpose, topic examples, and the optional birth-detail behavior. It could do more to disambiguate the many overlapping city/date alias parameters, but it is adequate for a zero-required-parameter read tool.

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 baseline is 3. The description restates pillar values for topic, but its example list includes 'dasha_analysis', which does not appear in the schema's topic enumeration ('inner_growth' does), a mild inconsistency that could mislead value selection.

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 resource ('Get deep personalized astrological interpretation') and scopes it to canonical life pillars with concrete examples. It is distinguishable from calculator siblings like calculate_chart or calculate_dasha, though it never explicitly says so.

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?

It notes the tool 'can be run with or without specific birth details' and maps to the /interpret slash command, which gives implied usage context. However it never states when to prefer this over ask_astrology_guidance or get_horoscope, nor any exclusions.

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

All ERUX Astrology & Ephemeris Engine 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.