Skip to main content
Glama
openfate-ai

OpenFate Bazi MCP

Official
by openfate-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Detect Bazi Interactions

detect_bazi_interactions
Read-onlyIdempotent

Identify Earthly Branch interactions in a Bazi chart—clashes, combinations, trines, punishments, destructions, and harms—across natal, annual, and Da Yun pillars.

Instructions

Detect raw Earthly Branch relationship occurrences for a natal chart and optional annual and Da Yun branches. Preserves every matching pillar position, including repeated branches. Covers clashes, six-combinations, the eight central-branch half-trines (COMBINATION_HALF), full trines, directionals, punishments, destructions, and harms. Results establish relationship presence, not weights, cancellation, or automatic transformation; targetElement is an affinity, not transformed energy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayBranchYesNatal day branch.
hourBranchNoNatal hour branch. Omit when birth time is unknown.
yearBranchYesNatal year branch.
dayunBranchNoOptional Da Yun branch. Preserved as the dayun pillar role, independently of the annual and natal branches.
monthBranchYesNatal month branch.
annualBranchNoOptional annual or target branch. Preserved as the annual pillar role, independently of repeated natal branches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • changedInput schema / properties / annualBranch / description
      Previous value: -"Optional annual or target branch for dynamic interaction detection."New value: +"Optional annual or target branch. Preserved as the annual pillar role, independently of repeated natal branches."
    • addedInput schema / properties / dayunBranch
      Added value: +{
+  "$ref": "#/properties/hourBranch",
+  "description": "Optional Da Yun branch. Preserved as the dayun pillar role, independently of the annual and natal branches."
+}
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish the safe, idempotent, closed-world read profile, yet the description adds real semantic context: results establish presence only, not weights, cancellation, or transformation, and targetElement is an affinity rather than transformed energy. It also notes that every matching pillar position, including repeated branches, is preserved — behavior no annotation conveys.

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?

Three sentences, front-loaded with the purpose, then an explicit coverage enumeration, then the interpretive caveats. The relationship-type list is long but each item earns its place by defining scope; little is wasted, though the enumeration could be trimmed.

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

Completeness4/5

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

There is no output schema, and the description compensates by explaining conceptually what the results represent (presence of relationships, preserved positions, affinity vs. transformed energy) and which relationship classes can appear. It is close to complete for an analytical tool, with only the exact return shape left implicit.

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 description coverage is 100%, with per-parameter descriptions for all six inputs, so the schema does the heavy lifting; baseline 3 applies. The description adds no parameter-level syntax or constraints, and its mention of targetElement refers to a field that is not among the input parameters, so it does not clarify invocation arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Detect) plus a precise resource (raw Earthly Branch relationship occurrences) and enumerates the exact relationship types covered, from clashes to harms. This scope is clearly distinct from the sibling tools, which compute charts, solar time, policies, resources, or reverse-solve times.

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?

The description implies when the tool is appropriate by describing its scope (raw relationship presence for a natal chart with optional annual/Da Yun branches), but it never states when to choose it over siblings like calculate_bazi_chart or what prerequisites apply. Usage must be inferred from domain knowledge.

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