Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Mental-Health Profile

astroway_wellness_mental_health
Read-onlyIdempotent

Calculate an elemental profile from luminaries plus Mercury, Venus, and Mars to identify dominant element, strengths, vulnerabilities, and coping patterns for mental wellness.

Instructions

Element-profile across luminaries + Mercury/Venus/Mars; identifies dominant element + strengths/vulnerabilities/coping.

[Group: Wellness] [Endpoint: POST /v1/wellness/mental-health] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]

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": {
      "date": "<date>",
      "time": "<time>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_wellness_mental_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
latitudeYes
timezoneNoIANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
cosmogramNo
longitudeYes
ayanamsaIdNo
zodiacTypeNo
houseSystemNoP
timezoneOffsetNoHours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
disclaimerNo
mentalProfileNo
elementProfileNo
dominantElementNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds two genuinely useful pieces beyond that: the cost (10 credits, Tier 1) and the exact required input set. It says nothing about interpretation style, whether sidereal/tropical defaults matter for a 'mental health' reading, or rate/limits behavior.

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?

Front-loaded and dense: one sentence of substance plus bracketed metadata for group, endpoint, required params and cost. Every line earns its place. It is arguably too terse rather than padded, but there is no filler.

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 return values need not be described. But for a 13-parameter, cost-bearing chart tool with heavy sibling overlap, the definition leaves an agent without enough to choose between this and the arroyo element siblings, or to know whether the ayanamsa/house-system choices change the mental-health framing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Thirteen parameters with only 23% schema description coverage, and the description only restates the four required fields already marked required in the schema. The philosophically significant knobs (ayanamsa school, zodiacType tropical vs sidereal, houseSystem, cosmogram) are left entirely unexplained, and the coverage gap is exactly where the description should have compensated.

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 names a specific computation: element profile over the luminaries plus Mercury/Venus/Mars, plus a dominant element and strengths/vulnerabilities/coping output. That is a clear verb-and-resource statement an agent can act on. However it does not distinguish itself from the very similarly named sibling astroway_psychological_modern_arroyo_element_balance (or arroyo_element_integration), which in a list of ~600 siblings is the main disambiguation risk.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative. Given that astroway_wellness_medical_astrology, astroway_wellness_yoga and the arroyo element tools all sit in adjacent territory, an agent is left to guess which to pick from the name alone.

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

Deploy Server

Other Tools