Skip to main content
Glama

acg_power_lines

Read-only

Compute astrocartography power lines (MC, AC, DC, IC) for a birth chart and return GeoJSON LineStrings tracing each planet's rising, setting, culminating, and anti-culminating lines globally. Use for map rendering or geographic analysis.

Instructions

Calculate Astrocartography power lines (MC, IC, AC/ASC, DC/DSC) for a natal chart. Returns GeoJSON LineStrings tracing each planetary angle line around the globe. These are the latitudinal lines where a planet was rising (AC), setting (DC), culminating (MC), or anti-culminating (IC) at birth.

❌ NOT FOR: 'Is [city] good for me?' or 'What planets affect me in Tokyo?' → For a specific city/location analysis, use acg_hits instead (faster and more relevant). ✅ USE FOR: Getting the full global GeoJSON line geometry for map rendering or bulk geographic analysis.

CREDIT COST: 10 credits per call.

EXAMPLE: Saturn and Jupiter power lines for a chart born 1990-04-15 in Chicago: birth_datetime='1990-04-15T14:30:00', birth_latitude=41.8781, birth_longitude=-87.6298, bodies=['Saturn', 'Jupiter']

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
birth_datetimeYesISO 8601 natal birth date/time.
birth_latitudeYesBirth latitude in decimal degrees.
birth_longitudeYesBirth longitude in decimal degrees.
bodiesNoList of celestial bodies for line calculation. E.g. ['Sun', 'Moon', 'Venus', 'Mars', 'Jupiter', 'Saturn']. Aliases: 'NorthNode'/'Node'/'Rahu' → MeanNode, 'SouthNode'/'Ketu' → SouthNode. Omit to use all classical planets.
query_latitudeNoFilter lines near this latitude (optional, for hits mode).
query_longitudeNoFilter lines near this longitude (optional, for hits mode).
radius_degNoSearch radius in degrees for hits filtering. Default 2°.
Behavior4/5

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

Annotations declare readOnlyHint=true, destructiveHint=false. Description adds credit cost (10 credits) and output format (GeoJSON LineStrings), extending beyond annotations without contradiction.

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?

Front-loaded purpose, followed by usage guidelines, credit cost, and example. No wasted words; efficient and well-structured.

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?

Covers parameters, usage, and output format. Could mention output structure more explicitly, but example and description suffice. No output schema, but description explains returns.

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

Parameters4/5

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

100% schema coverage, so baseline 3. Description adds example usage, explains optional parameters (query_latitude, radius_deg) and aliases for bodies, adding value.

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?

Description clearly states it calculates astrocartography power lines (MC, IC, AC/ASC, DC/DSC) and returns GeoJSON LineStrings. It distinguishes from sibling tool acg_hits by explicitly stating not for location-specific analysis.

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

Usage Guidelines5/5

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

Explicitly says when to use (global line geometry) and when not (specific city/location), and provides alternative (acg_hits) with reasoning.

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/openephemeris/openephemeris-MCP'

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