AstroWay Divination and esoterica

Yearly Hexagram

astroway_iching_yearly

Read-onlyIdempotent

A hexagram for a person and a year: the Mei Hua formula with the earthly branch of the year asked about in place of the year of asking and the lunar month, day and hour of birth. Labelled basis: convention: Mei Hua casts for a question, and this annual use is this API's convention. Returns the full Legge reading and ti/yong.

[Group: I Ching (Standalone)] [Endpoint: POST /v1/iching/yearly] [Required: birthDate, birthTime, year] [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": {
      "birthDate": "<birthDate>",
      "birthTime": "<birthTime>",
      "year": "<year>"
    },
    "name": "astroway_iching_yearly"
  }
}

Input Schema

Name	Required	Description
`year`	Yes	The year the reading is for, by its earthly branch.
`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.
`birthDate`	Yes
`birthTime`	Yes	Birth time; gives the hour term of the cast.
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`timezoneOffset`	No	Hours from UTC at the birthplace; places the lunar birth day. Defaults to 8.

Output Schema

Name	Required	Description	Default
`year`	No
`basis`	No
`focus`	No
`lines`	No
`terms`	No
`method`	No
`source`	No
`tiYong`	No
`primary`	No
`birthDate`	No
`resulting`	No
`lunarBirth`	No
`yearBranch`	No
`meiHuaSource`	No
`changingLines`	No
`readingRuleSource`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds context beyond that: the `basis: convention` provenance label, the return contents (full Legge reading and ti/yong), and the 10-credit Tier 1 cost, which an agent needs before invoking a metered call.

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 core explanation is front-loaded and dense but readable, with metadata (group, endpoint, required, cost) cleanly bracketed afterward. The '[Required: ...]' line restates the schema's required array, which is slightly redundant, but overall there is little wasted prose.

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?

An output schema exists, so the description only needs to gesture at returns, which it does ('full Legge reading and ti/yong'). Combined with cost, endpoint, method, and the convention caveat, an agent has everything needed to decide whether to call it and what it will get back.

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?

Schema description coverage is 83%, so the baseline is 3, but the description adds real meaning by explaining how inputs feed the formula: the year contributes its earthly branch, and birth time supplies the 'hour term of the cast', alongside lunar month/day/hour of birth. Minor gap: it does not mention timezoneOffset or the compact-mode fields/precision parameters at all.

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 artifact (a hexagram for a person and a given year) and specifies the derivation method (Mei Hua formula with the year's earthly branch substituted for the year of asking). It implicitly separates itself from question-based casting siblings by explaining the substitution, but it never names a sibling such as astroway_iching_plum_blossom or astroway_iching_daily directly.

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?

It conveys the usage context (annual reading, 'this API's convention' rather than a classical Mei Hua question cast, flagged as `basis: convention`), which is genuinely useful framing. However, there is no explicit when-to-use/when-not guidance versus the many I Ching siblings, and no stated prerequisites beyond the required-parameter list.

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

All AstroWay Divination and esoterica 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?