AstroWay Astrology API (full catalogue)

Transit Midpoints

astroway_cosmobiology_transit_midpoints

Read-onlyIdempotent

Transits hitting natal midpoints in 90° dial.

[Group: Cosmobiology / Hamburg School] [Endpoint: POST /v1/cosmobiology/transit-midpoints] [Required: date, time, latitude, longitude, targetDate] [Cost: 10 credits (Tier 1)]

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>",
      "targetDate": "<targetDate>"
    },
    "name": "astroway_cosmobiology_transit_midpoints"
  }
}

Input Schema

Name	Required	Description	Default
`city`	No
`date`	Yes
`name`	No
`time`	Yes
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`withTnp`	No
`ayanamsa`	No	Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
`converse`	No
`latitude`	Yes
`timezone`	No	IANA 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.
`cosmogram`	No
`longitude`	Yes
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`ayanamsaId`	No
`targetDate`	Yes
`targetTime`	No
`zodiacType`	No
`houseSystem`	No		P
`targetTzOffset`	No
`timezoneOffset`	No	Hours 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

Name	Required	Description	Default
`orb`	No
`hits`	No
`count`	No
`source`	No
`targetDate`	No
`methodology`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedNov 7, 2026

removedInput schema / properties / ayanamsaId / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / ayanamsaId / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedInput schema / properties / targetTzOffset / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / targetTzOffset / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / count / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / count / type
```
Added value: +[
+  "number",
+  "null"
+]
```

changedOutput schema / properties / hits / anyOf

Previous value: -[
-  {
-    "items": {
-      "anyOf": [
-        {
-          "additionalProperties": {},
-          "properties": {
-            "midpointLongitude": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "midpointLongitude90": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "natalMidpointOf": {
-              "anyOf": [
-                {
-                  "items": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ]
-                  },
-                  "type": "array"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "orb": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "transit": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "midpointLongitude": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "midpointLongitude90": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "natalMidpointOf": {
+              "anyOf": [
+                {
+                  "items": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "type": "array"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "orb": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "transit": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / methodology / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / methodology / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / orb / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / orb / type

Added value: +[
+  "number",
+  "null"
+]

removedOutput schema / properties / source / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / source / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / targetDate / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / targetDate / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedOct 5, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), so the description only needs to add context. It contributes the cost (10 credits, Tier 1) and the required-input list, which are genuinely useful for planning, but says nothing about result shape, precision of orbs, or how targetDate interacts with date.

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 is short and front-loaded: the core statement comes first, followed by clearly bracketed metadata lines. Nothing is padded, though the four bracket lines are largely redundant with the schema and annotations.

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?

For a 20-parameter specialized cosmobiology endpoint, the description is thin. An output schema exists so return values need not be explained, but the meaning of the two dates, the dial convention, and the defaults an agent should rely on are all absent, leaving the caller to guess on a paid, credit-consuming call.

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?

With 20 parameters and only 25% schema coverage, the description needs to carry real parameter meaning, and it does not. The only parameter content is a restatement of the five required fields already declared in the schema; the distinction between date and targetDate, and the roles of targetTime, converse, cosmogram, withTnp, houseSystem, and targetTzOffset, are left unexplained.

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 a specific verb and resource: transits contacting natal midpoints measured on a 90° dial. That is concrete enough to distinguish it from generic transit or midpoint-picture work, although it never names the closest siblings (midpoint_pictures, dial_90) to draw the boundary explicitly.

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 guidance at all: nothing says to pick this over midpoint_pictures or dial_90, no preconditions, no note about which chart inputs are needed. The bracket metadata (group, endpoint, required fields, cost) is administrative, not usage guidance.

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

All AstroWay Astrology API (full catalogue) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?