Skip to main content
Glama

AstroLogics

Yogas in a birth chart

get_yogas
Read-onlyIdempotent

List the classical yogas present in a birth chart (for example Gaja Kesari, Raja and Dhana yogas) with the planets that form each, its strength and its traditional meaning. Uses a saved chart from the signed-in user's AstroLogics account or given birth details, with the chart features of the user's plan.

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
dateNoBirth date, YYYY-MM-DD (when not using a saved chart).
timeNoLocal birth time, HH:MM (when not using a saved chart).
chartNoA saved chart's id or name from list_my_charts. Or give the birth details below instead.
languageNoSet to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.
latitudeNoBirth latitude in decimal degrees (when not using a saved chart).
longitudeNoBirth longitude in decimal degrees (when not using a saved chart).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, yet the description still adds meaningful context: it requires a signed-in AstroLogics account, is gated by "the chart features of the user's plan", and discloses the shape of the result (planets, strength, meaning). It does not mention rate limits or what happens when a plan lacks the feature.

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?

Two sentences, front-loaded with the output content before the input options, with no filler. The trailing clause "with the chart features of the user's plan" is slightly vague and could be sharpened, but nothing is redundant.

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?

With no output schema, the description usefully sketches the return payload, and annotations plus a fully documented schema carry the rest. The main gap is that all six parameters are optional, yet the description never says what happens when the tool is called with nothing (does it default to the user's saved chart?).

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 chart id/name, date, time, latitude/longitude and the Hindi enum. The description only restates the chart-vs-birth-details alternative ("a saved chart ... or given birth details"), adding no syntax, precedence, or defaulting rules.

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 ("List the classical yogas present in a birth chart") and enumerates what each result contains (forming planets, strength, traditional meaning), plus named examples (Gaja Kesari, Raja, Dhana). It is clearly distinguishable from the check_* dosha siblings by resource, though it never explicitly contrasts itself with 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 only implied: an agent can infer this is for chart analysis of auspicious combinations rather than afflictions. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative sibling (e.g. get_birth_chart for raw placements). The input-sourcing sentence addresses parameters, not tool selection.

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.

Resources