Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Branch and stem interactions

astroway_bazi_interactions
Read-onlyIdempotent

Detect stem combinations, harmonies, trines, clashes, harms, punishments and self-punishments in a BaZi chart, including involved pillars and the element a combination produces.

Instructions

Stem combinations, six harmonies, full and half trines, three-branch seasons (三會), clashes, harms, punishments and self-punishments present in the chart, with the pillars involved and the element a combination produces.

[Group: BaZi (Four Pillars)] [Endpoint: POST /v1/bazi/interactions] [Required: date] [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>"
    },
    "name": "astroway_bazi_interactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
timeNo
genderNo
languageNo
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.
longitudeNo
dayBoundaryNo
includeLuckNo
stageSchoolNo
trueSolarTimeNo
timezoneOffsetNoIgnored when timezone is sent.
includeFullTableNo

Output Schema

NameRequiredDescriptionDefault
notesNo
sourceNo
pillarsNo
solarYearNo
disclaimerNo
methodologyNo
interactionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds genuinely useful non-annotation facts: the endpoint, the 10-credit Tier 1 cost, and that the response includes the pillars involved and the element a combination produces. It does not address permissions, rate limits, or what happens when optional parameters are omitted.

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?

Content is front-loaded in a single dense sentence that enumerates outputs, followed by structured bracketed metadata for group, endpoint, required input, and cost. The interaction list is long but each term earns its place by defining coverage; only the metadata block borders on boilerplate.

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 12-parameter, domain-heavy BaZi tool, the description explains the return contents adequately (and an output schema exists, so return values need not be spelled out) but says nothing about the many optional parameters that materially affect results. An agent could call it, but not call it correctly for anything beyond a bare date.

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 12 parameters and only 17% schema description coverage, the description carries the burden of explaining parameters but only echoes the required 'date'. Domain-critical switches like dayBoundary, stageSchool, trueSolarTime, includeLuck, and includeFullTable go unexplained in both the description and the schema, so the agent cannot tell how they alter results.

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 the specific resource (stem and branch interactions in a chart) and enumerates the interaction types it reports (combinations, six harmonies, trines, 三會, clashes, harms, punishments), so the agent knows exactly what data comes back. It does not explicitly distinguish itself from siblings like astroway_bazi_four_pillars or astroway_bazi_chart, leaving that differentiation to inference.

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 statement of when to call this versus the many other BaZi tools, nor any prerequisite or exclusion. The only structural hint is '[Required: date]', which merely restates the schema and gives no usage context.

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

Deploy Server

Other Tools