Skip to main content
Glama

ERUX Astrology & Ephemeris Engine

ask_astrology_guidance

Read-onlyIdempotent

Provide authentic, deterministic astrological framework guidance for any life question (e.g. career shift, relationship milestones, financial timing, health/somatic wellness, relocation). Corresponds to the /ask slash command in Discord, Telegram, and Google Chat. Explains which astrological houses, ruling planetary significators (Karakas), and timing triggers govern the user's inquiry. If birth details are included in the question or parameters, also computes the native's actual natal placements and active Vimshottari Dasha.

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": {
      "question": "<question>"
    },
    "name": "ask_astrology_guidance"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional natal birth city for personalized chart grounding
dateNoOptional natal birth date (YYYY-MM-DD) for personalized house & Dasha evaluation
timeNoOptional natal birth time (HH:MM, default '12:00')12:00
questionYesAstrological or life guidance question to analyze (e.g. 'When will my career shift?', 'What does my 10th house indicate?')

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / city
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional natal birth city for personalized chart grounding",
      +  "title": "City"
      +}
    • addedInput schema / properties / date
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional natal birth date (YYYY-MM-DD) for personalized house & Dasha evaluation",
      +  "title": "Date"
      +}
    • 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"
      -}
    • addedInput schema / properties / time
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": "12:00",
      +  "description": "Optional natal birth time (HH:MM, default '12:00')",
      +  "title": "Time"
      +}
  2. Changed2 schema fields changed
    • 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 / question / description
      Added value: +"Astrological or life guidance question to analyze (e.g. 'When will my career shift?', 'What does my 10th house indicate?')"
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile needs no restating. The description adds real value by disclosing the conditional branch — natal placements and active Vimshottari Dasha are only computed when birth details are supplied — and by noting the Discord/Telegram/Google Chat slash-command correspondence. It stops short of describing depth, determinism limits, or output characteristics beyond 'deterministic'.

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?

Four tightly packed sentences, front-loaded with the core purpose before the platform note and conditional behavior. No filler, though the example-domain list and slash-command sentence are somewhat dense and could be trimmed without losing meaning.

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?

Given that an output schema exists and annotations cover the safety profile, the description need not explain return values. It covers purpose, scope, domains, platform mapping, and the conditional natal computation, leaving only the relationship to the sibling calculation tools unaddressed for this fairly complex tool.

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 each parameter is already documented, establishing a baseline of 3. The description lifts this slightly by explaining the functional consequence of supplying city/date/time — that the tool then computes actual natal placements and active Dasha rather than generic framework guidance — which tells the agent why those optional parameters are worth filling.

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 pair ('provide astrological framework guidance') and enumerates concrete deliverables: which houses, Karakas, and timing triggers govern the inquiry, plus conditional natal/Dasha computation. It is clear what the tool does, but it never names or contrasts with the overlapping siblings calculate_chart and calculate_dasha, so an agent cannot fully tell when this tool supersedes them.

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?

Usage is implied by 'for any life question' and the parenthetical example domains (career, relationships, financial timing, health, relocation), which give useful context. However, there is no explicit when-to-use/when-not guidance and no routing to the alternative chart/Dasha tools that compute similar outputs.

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.