Skip to main content
Glama
astroway

astroway-mcp

Official

Heliocentric Chart

heliocentric
Read-onlyIdempotent

Determine heliocentric (Sun-centered) planetary positions for a given birth moment, with Earth replacing the Sun and the Moon excluded.

Instructions

Calculate heliocentric planetary positions (Sun-centered) for a given birth moment. Earth replaces Sun; Moon is excluded.

[Group: Specialized Charts] [Cost: 20 credits (Tier 2)]

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
timeYes
timezoneOffsetNo
latitudeNo
longitudeNo
houseSystemNoP
nameNo
cityNo
zodiacTypeNo
ayanamsaIdNo
cosmogramNo
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds that Earth replaces Sun and Moon is excluded, plus cost tier. This supplements annotations well, no contradiction.

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?

The description is short (two sentences) with group and cost metadata and an example. It is front-loaded with purpose. Could omit the example if not adding value, but overall efficient.

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?

Given 11 parameters, no output schema, and complex astrological content, the description lacks details on return format, house system handling, or coordinate usage. Incomplete for a tool of this complexity.

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?

Schema has 11 parameters with 0% description coverage. The description does not explain any parameter meaning but provides an example request body. With such low coverage, the description should clarify key optional parameters like 'zodiacType' or 'houseSystem'.

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 states the tool calculates heliocentric (Sun-centered) planetary positions for a birth moment, specifying that Earth replaces Sun and Moon is excluded. This distinguishes it from other chart tools.

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?

The description mentions it's a specialized chart and costs 20 credits, but provides no explicit guidance on when to use this tool versus alternatives like 'chart' or 'draconic'. The sibling list is large but not referenced.

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