AstroWay Astrology API (full catalogue)

Trutine of Hermes

astroway_prognostics_rectification_trutine

Read-onlyIdempotent

Apply the Trutine of Hermes (Animodar) technique to derive the birth time from the Moon's prenatal syzygy position.

[Group: Prognostics] [Endpoint: POST /v1/rectification/trutine] [Required: date, time, latitude, longitude] [Cost: 250 credits (Tier 5)] ⚠️ Heavy — confirm with user before invoking.

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_prognostics_rectification_trutine"
  }
}

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.
`ayanamsa`	No	Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
`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
`zodiacType`	No
`houseSystem`	No		P
`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
`syzygyDate`	No
`syzygyType`	No
`moonAtSyzygy`	No
`correctedTime`	No
`correctedAscendant`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 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"
+]
```

removedOutput schema / properties / correctedAscendant / anyOf

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

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

removedOutput schema / properties / correctedTime / anyOf

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

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

removedOutput schema / properties / moonAtSyzygy / anyOf

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

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

removedOutput schema / properties / syzygyDate / anyOf

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

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

removedOutput schema / properties / syzygyType / anyOf

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

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

First observedOct 5, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds value the annotations cannot: a concrete price (250 credits, Tier 5), a heavyweight flag with an explicit confirm-with-user instruction, and the endpoint. It stops short of saying anything about the result or how long such a call takes.

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 technique statement is front-loaded in one clean sentence, and the bracketed metadata lines are scannable. The '[Required: ...]' line duplicates the schema's required array, which is the only genuinely redundant element.

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?

Output schema exists, so return values need not be explained. Still, for a 15-parameter, expensive, specialized rectification technique, the description leaves unclear whether the caller must already know an approximate birth time, and what the derived time's precision or confidence means — gaps that matter before spending 250 credits.

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?

Schema description coverage is only 33% across 15 parameters, so the description needs to compensate and does not. It merely repeats the four required fields already listed in the schema's 'required' array and says nothing about the undocumented parameters (city, name, cosmogram, zodiacType, ayanamsaId, houseSystem) or about how ayanamsa/houseSystem choices affect a rectification result.

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 names a specific technique (Trutine of Hermes / Animodar) and a specific outcome (deriving birth time from the Moon's prenatal syzygy), which is far more than restating the title. It does not, however, distinguish itself from the sibling astroway_prognostics_rectification tool, so an agent cannot tell from the text which rectification method to pick.

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

Usage Guidelines3/5

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

There is a real usage gate in 'confirm with user before invoking' and a cost warning, which is more than most definitions offer. But there is no statement of when this technique should be preferred over the generic rectification sibling, or what inputs are prerequisites (e.g. a known approximate birth time), leaving selection largely implied.

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?