Skip to main content
Glama

acg_hits

Read-only

Find all astrocartography lines (power and aspect) near a location. Results sorted by distance reveal planetary influences, enabling interpretation of how a place connects to a birth chart.

Instructions

Find all Astrocartography lines (power lines + aspect lines) passing near a specific location. Returns features sorted by distance, making it easy to interpret planetary influences at a place.

✅ USE THIS TOOL FOR: 'Is [city] good for me?', 'What planets affect me in Tokyo?', 'What ACG lines run through Paris for my chart?', 'Which cities are under my Jupiter line?' ❌ NOT FOR: Full global map geometry → use acg_power_lines for that instead.

CREDIT COST: 15 credits per call.

EXAMPLE: All ACG lines within 3° of Paris for a chart born 1990-04-15 in Chicago: birth_datetime='1990-04-15T14:30:00', birth_latitude=41.8781, birth_longitude=-87.6298, query_latitude=48.8566, query_longitude=2.3522, radius_deg=3

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
birth_datetimeYesISO 8601 natal birth date/time.
birth_latitudeYesBirth latitude in decimal degrees.
birth_longitudeYesBirth longitude in decimal degrees.
query_latitudeYesLatitude of the location to check for nearby lines.
query_longitudeYesLongitude of the location to check for nearby lines.
radius_degNoSearch radius in degrees (default 2°, max 90°).
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.
include_aspectsNoInclude aspect lines in results (default true).
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful context like credit cost (15 credits) and an example call, which enhances transparency 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.

Conciseness5/5

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

Description is well-structured with sections for when to use, when not to, credit cost, and an example. It is concise without fluff.

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

Completeness5/5

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

Given good annotations, 100% schema coverage, and a clear description with usage guidance, credit cost, and an example, the context is fully sufficient for correct tool invocation.

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%, so baseline is 3. The description includes an example but does not add additional parameter explanations beyond what the schema provides. No extra semantics added.

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 states it finds all Astrocartography lines near a location, sorted by distance. It clearly distinguishes from the sibling tool 'acg_power_lines' which is for full global map geometry.

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 provides example queries for when to use (e.g., 'Is [city] good for me?') and explicitly says NOT for full global map geometry, directing to the sibling tool.

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