Skip to main content
Glama
astroway

astroway-mcp

Official

Generate Money Report (PDF or HTML)

reports_money

Analyze financial astrology focusing on second house earned income, eighth house shared resources, Jupiter expansion, and Saturn discipline. Not investment advice.

Instructions

Financial natal: 2nd house (earned income), 8th house (shared resources), Jupiter (expansion), Saturn (discipline). Disclaimer: not investment advice.

[Group: Reports] [Cost: 5,000 credits (Tier 7)] ⚠️ Premium — ~50% of free monthly budget. Confirm with user before invoking.

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

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)
Behavior3/5

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

Annotations already indicate it's not read-only and not destructive. The description adds a disclaimer ('not investment advice') and cost warning but does not disclose behavioral traits like rate limits or response format. With annotations present, the description meets the minimum but adds little extra context.

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

Conciseness3/5

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

The description mixes content overview, disclaimer, group tag, cost warning, and example in a somewhat cluttered manner. It could be more streamlined, but it's not excessively long. The cost warning is necessary but disrupts flow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is present, yet the description does not clarify what the tool returns (e.g., PDF link, HTML content). It mentions output format (PDF or HTML) only in the title. Without details on output structure or delivery, the description is incomplete for an agent to fully understand the tool's behavior.

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?

The input schema has 100% coverage, fully documenting all 7 parameters. The description includes an example request but does not add semantic meaning beyond the schema, so baseline 3.

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 title and description clearly indicate that the tool generates a financial report based on birth chart placements (2nd house, Jupiter, Saturn). However, it does not distinguish from sibling financial tools like financial_career_money_style, limiting clarity for selection.

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

Usage Guidelines4/5

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

The description explicitly warns about the high cost (5,000 credits) and instructs to confirm with the user before invoking, which is strong guidance on when to use. It lacks when-not-to-use or alternative options, but the cost warning is valuable.

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