Skip to main content
Glama

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.

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_interpretation"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional birth city for natal chart mapping
dateNoOptional birth date in YYYY-MM-DD format for personalized placements
timeNoOptional birth time in 24-hour HH:MM format (default '12:00')12:00
topicNoCanonical life pillar: 'career_and_vocation', 'relationships', 'wealth_and_finance', 'health_and_vitality', or 'inner_growth'career_and_vocation
systemNoAstrological coordinate framework: 'hybrid', 'vedic', or 'western'hybrid
birth_cityNoExplicit alias for natal birth city
birth_dateNoExplicit alias for natal birth date (YYYY-MM-DD)
target_cityNoAlias for current relocated city
current_cityNoCurrent relocated city
birth_countryNoExplicit alias for natal birth country

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / platform
      Removed 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"
      -}
    • removedInput schema / properties / user_prompt
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Raw user query for intent arbitration",
      -  "title": "User Prompt"
      -}
  2. Changed12 schema fields changed
    • 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"
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds two useful behavioral facts: it mirrors a Discord/Google Chat slash command, and it works without birth details (implying sensible defaults). It says nothing about depth, latency, or what happens when only partial birth data is supplied.

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 and followed by the pillar examples that matter most for selection. No filler or restated name. The slash-command sentence is the weakest, but it still carries environment-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Ten parameters with four overlapping location aliases (city, birth_city, current_city, target_city) and no required fields create real ambiguity about precedence, which the description does not address. An output schema exists, so return values need not be explained. Adequate but leaves the alias-resolution question for the agent to guess.

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 and the schema already explains topic, system, and every birth-city alias. The description's only parameter-adjacent contribution is the pillar examples, and one of them ('dasha_analysis') is not in the schema's topic list while 'inner_growth' is omitted, which slightly muddies rather than clarifies the topic parameter.

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 uses a specific verb+resource ('Get deep personalized astrological interpretation') and enumerates the canonical life pillars, so an agent knows exactly what the tool returns. It also anchors the tool to the /interpret slash command, which helps recognition. It stops short of naming which sibling to prefer over it (e.g. get_horoscope or ask_astrology_guidance), so differentiation is implicit.

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?

One genuine usage signal is given: 'Can be run with or without specific birth details,' which tells the agent the call is safe with zero arguments. There is no guidance on when to choose this over get_horoscope, calculate_chart, or ask_astrology_guidance, and no exclusions. Usage is therefore implied rather than stated.

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.