Skip to main content
Glama
astroway

astroway-mcp

Official

Mental-Health Profile

wellness_mental_health
Read-onlyIdempotent

Analyze your birth chart's elemental balance to identify mental health strengths, vulnerabilities, and coping strategies based on planetary positions.

Instructions

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

[Group: Wellness]

Example request body: {"date":"1990-05-15","time":"14:30:00","timezoneOffset":3,"latitude":50.45,"longitude":30.52}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesBirth date YYYY-MM-DD
timeYesBirth time HH:mm:ss (local)
timezoneOffsetNoUTC offset in hours (e.g. 3 for UTC+3, -5 for EST)
latitudeNoBirth latitude in decimal degrees
longitudeNoBirth longitude in decimal degrees
houseSystemNoHouse system: P=Placidus (default), K=Koch, W=Whole Sign, E=Equal
cityNoCity name (display only)
Behavior4/5

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

Annotations already confirm read-only, safe operation. The description adds value by detailing the output dimensions (dominant element, strengths, vulnerabilities, coping) beyond what annotations convey, even though no output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences plus a group tag and example. It front-loads the core purpose with no redundant or verbose phrasing.

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 the absence of an output schema, the description provides a reasonable overview of what the tool returns. However, it could be more explicit about the format or structure of the output, such as whether it includes textual descriptions or numeric scores.

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% with clear parameter descriptions. The description does not add new semantic meaning to the parameters beyond the example request body, which is illustrative but not semantically additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies the tool's purpose: creating an element profile focused on luminaries (Sun, Moon) and personal planets (Mercury, Venus, Mars), and identifying dominant element, strengths, vulnerabilities, and coping. This distinguishes it from other wellness tools like wellness_medical_astrology or wellness_diet.

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?

The description provides no guidance on when to use this tool versus alternatives such as wellness_cycle or wellness_herbs. The group label 'Wellness' is present but no explicit context for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/astroway/astroway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server