Skip to main content
Glama
astroway

astroway-mcp

Official

Nodal Axis Detail

evolutionary_nodal_axis_detail
Read-onlyIdempotent

Get detailed evolutionary astrology analysis of North and South Nodes including rulers and conjuncts by providing natal chart data.

Instructions

Full NN/SN with rulers + conjuncts.

[Group: Evolutionary Astrology]

Example request body: {"...chart":"..."}

Input Schema

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

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

Annotations indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=false. The description only adds 'Full NN/SN with rulers + conjuncts', which aligns but does not disclose any additional behavioral traits such as output format, pagination, or error handling. Minimal value beyond annotations.

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 is extremely concise (about 10 words plus a group label and example), but this brevity sacrifices useful content. It lacks structure beyond the group label. While it is front-loaded, it does not earn its place as it omits critical details.

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

Completeness1/5

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

The tool has 11 parameters, no output schema, and no parameter descriptions. For a complex astrology calculation tool, the description is severely inadequate. It fails to provide enough context for an agent to correctly invoke the tool or understand its output.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain any of the 11 parameters. The example request body is a placeholder with no actual parameter values. The agent receives no guidance on how to fill parameters like 'date', 'time', or 'houseSystem'.

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 states 'Full NN/SN with rulers + conjuncts', clearly indicating it provides nodal axis details with rulers and conjuncts. The title 'Nodal Axis Detail' reinforces this. However, it does not differentiate from sibling tools like 'evolutionary_pluto_natal_condition' or 'evolutionary_skipped_steps', lacking explicit distinction.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, exclusions, or typical use cases. Given the extensive sibling list, the agent would need to infer usage from the tool name alone.

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