Skip to main content
Glama

AstroWay Core astrology

Astrocartography (A*C*G)

astroway_geo_acg
Read-onlyIdempotent

Calculate ACG lines for all planets: the geodetic map lines where each planet was on an angle at birth.

[Group: Astro-Geography] [Endpoint: POST /v1/acg] [Required: date, time, latitude, longitude] [Cost: 50 credits (Tier 3)]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>",
      "time": "<time>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_geo_acg"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
latitudeYes
timezoneNoIANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
cosmogramNo
longitudeYes
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
ayanamsaIdNo
zodiacTypeNo
houseSystemNoP
timezoneOffsetNoHours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
linesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / ayanamsaId / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / ayanamsaId / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / lines / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "additionalProperties": {},
      -          "properties": {
      -            "coordinates": {
      -              "anyOf": [
      -                {
      -                  "items": {
      -                    "anyOf": [
      -                      {
      -                        "items": {
      -                          "anyOf": [
      -                            {
      -                              "type": "number"
      -                            },
      -                            {
      -                              "type": "null"
      -                            }
      -                          ]
      -                        },
      -                        "type": "array"
      -                      },
      -                      {
      -                        "type": "null"
      -                      }
      -                    ]
      -                  },
      -                  "type": "array"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "planet": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "planetId": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "type": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            }
      -          },
      -          "type": "object"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "coordinates": {
      +              "anyOf": [
      +                {
      +                  "items": {
      +                    "anyOf": [
      +                      {
      +                        "items": {
      +                          "type": [
      +                            "number",
      +                            "null"
      +                          ]
      +                        },
      +                        "type": "array"
      +                      },
      +                      {
      +                        "type": "null"
      +                      }
      +                    ]
      +                  },
      +                  "type": "array"
      +                },
      +                {
      +                  "type": "null"
      +                }
      +              ]
      +            },
      +            "planet": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "planetId": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "type": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's main contribution is the cost disclosure — '50 credits (Tier 3)' — plus the endpoint path, which are genuinely useful and not in the annotations. It says nothing further about latency, caching, or how heavy a full all-planet computation is.

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 definition sentence is front-loaded and waste-free, and the bracketed metadata block is scannable. The group/endpoint/required lines repeat structured information an agent already has, costing a little density.

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

Completeness3/5

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

With 15 parameters, three enums and a sidereal/tropical switch, this is a complex call, and the description leaves the agent to discover the tropical-vs-sidereal choice, the default Lahiri ayanamsa, and the timezone resolution rules entirely from the schema. An output schema exists, so return-value explanation is rightly omitted, but the input-side configuration story is thin.

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 only 33% across 15 parameters, so the description needed to compensate, and it does not. Its parameter content ('Required: date, time, latitude, longitude') merely restates the schema's required array and adds no meaning for ayanamsa, zodiacType, houseSystem, cosmogram, fields, precision, or the timezone vs. timezoneOffset interplay.

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?

States a specific verb and resource ('Calculate A*C*G lines') and adds a real gloss — 'the geodetic map lines where each planet was on an angle at birth' — which tells an agent what the output means. 'For all planets' implicitly distinguishes it from astroway_geo_solar_acg, but it never names that or any other geo sibling (acg_line_report, acg_zones, geodetic, parans) to route the agent.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance at all, despite a dense cluster of near-neighbours (acg_best_places, acg_by_category, acg_line_report, solar_acg, relocation). Only a prerequisites-style line ('Required: date, time, latitude, longitude') is present, which is already enforced by the schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources