Skip to main content
Glama

ERUX Astrology & Ephemeris Engine

get_yogas

Read-onlyIdempotent

Identify auspicious & powerful classical Vedic Yogas present in a birth or mundane chart (e.g. Raja Yogas, Dhana Yogas, Pancha Mahapurusha Yogas, Gaja Kesari, Budhaditya). Corresponds to the /yogas slash command in Discord and Google Chat. Requires birth details ('date', 'time', 'city') or country name ('country'). Returns active yogas, classical definitions, and link to ERUX divisional varga breakdown.

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

Input Schema

NameRequiredDescriptionDefault
cityNoBirth city or founding location
dateNoNatal birth date or event founding date in YYYY-MM-DD format
timeNoBirth time in 24-hour HH:MM format (default '12:00')12:00
countryNoCountry name for personal birth city disambiguation or national mundane chart
birth_cityNoExplicit alias for natal birth city
birth_dateNoExplicit alias for natal birth date (YYYY-MM-DD)
birth_timeNoExplicit alias for natal birth time (HH:MM)
birth_countryNoExplicit alias for natal birth country

Output Schema

NameRequiredDescriptionDefault
resultYes

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": "Raw user query for intent arbitration",
      -  "title": "User Prompt"
      -}
  2. Changed9 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 / birth_time / description
      Added value: +"Explicit alias for natal birth time (HH:MM)"
    • addedInput schema / properties / city / description
      Added value: +"Birth city or founding location"
    • addedInput schema / properties / country / description
      Added value: +"Country name for personal birth city disambiguation or national mundane chart"
    • addedInput schema / properties / date / description
      Added value: +"Natal birth date or event founding date in YYYY-MM-DD format"
    • addedInput schema / properties / time / description
      Added value: +"Birth time in 24-hour HH:MM format (default '12:00')"
    • 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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds what the output contains ('active yogas, classical definitions, and link to ERUX divisional varga breakdown') and the input prerequisite, but is silent on failure behavior (e.g., unknown city, missing time) and does not reconcile the claimed 'requires' inputs with the schema where all parameters are optional with defaults.

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, front-loaded with purpose, followed by examples and then the input requirement—an efficient ordering. The Discord/Google Chat slash-command sentence is the weakest addition, though it does help an agent explain invocation to users.

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?

An output schema exists, so describing return values is a bonus rather than a requirement. The gap is around invocation ambiguity: eight parameters containing two parallel naming schemes, all optional with a '12:00' time default, while the description says details are 'required' and never explains precedence or fallback when only country is supplied.

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 coverage is 100%, so the schema already documents all eight parameters, giving a baseline of 3. The description adds the useful either/or input pattern (birth date/time/city versus country for a mundane chart) but never mentions the birth_* alias family or explains when to use aliases versus the short names, leaving the duplication unresolved.

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 ('Identify auspicious & powerful classical Vedic Yogas present in a birth or mundane chart') and enumerates concrete examples (Raja, Dhana, Pancha Mahapurusha, Gaja Kesari, Budhaditya). It does not explicitly contrast with siblings like calculate_chart or get_horoscope, so the agent must infer the boundary, but the domain is unambiguous.

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?

Gives a precondition ('Requires birth details ... or country name') which tells the agent what input is needed, so usage is implied. However there is no guidance on when to prefer this over get_horoscope or calculate_chart, and no exclusions. The Discord/Google Chat slash-command mapping is provenance, not selection guidance.

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.