Skip to main content
Glama
bazi-solar-term-mcp

bazi-solar-term-mcp

audit_llm_bazi_answer

Audit LLM or human BaZi Four Pillars claims against astronomical ground truth and report which Year, Month, Day, or Hour pillar or Day Master was miscalculated.

Instructions

Verify an LLM or human-computed BaZi Four Pillars chart against exact astronomical ground truth and report which pillars or Day Master were miscalculated.

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": {
      "birthDateTime": "<birthDateTime>",
      "claimedYear": "<claimedYear>",
      "claimedMonth": "<claimedMonth>",
      "claimedDay": "<claimedDay>"
    },
    "name": "audit_llm_bazi_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional birthplace city.
timeZoneNoOptional explicit IANA time zone.
longitudeNoOptional explicit longitude.
claimedDayYesClaimed Day Pillar GanZhi (e.g., "戊午").
claimedHourNoOptional claimed Hour Pillar GanZhi (e.g., "壬子").
claimedYearYesClaimed Year Pillar GanZhi (e.g., "丙子").
claimedMonthYesClaimed Month Pillar GanZhi (e.g., "庚寅").
birthDateTimeYesBirth date/time in "YYYY-MM-DD HH:mm".
useTrueSolarTimeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the return content by promising a report of which pillars or Day Master were miscalculated. It says nothing about whether the tool mutates state, how missing location inputs (city vs. longitude vs. timeZone) are resolved, or how it behaves when optional claimed fields are absent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; every clause contributes (subject, comparison baseline, and reported outcome).

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?

For a read-only verification tool with no output schema, the description adequately conveys what comes back (per-pillar/Day Master mismatch reporting). The main residual gap is the precedence and fallback behavior among the optional location and time-zone parameters, which matters given 9 parameters.

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 89%, so the schema already documents the GanZhi formats, the birthDateTime string format, and the useTrueSolarTime default. The description adds no parameter-level meaning beyond that, which is the baseline expectation at this coverage level.

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?

States a specific verb (verify/audit) and resource (BaZi Four Pillars chart) plus the comparison target (astronomical ground truth) and the output focus (which pillars or Day Master are wrong). This implicitly separates it from calculate_bazi_chart, since it consumes a claimed chart rather than producing one, though no sibling is named explicitly.

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 phrase 'LLM or human-computed chart' implies the tool is for validating an existing claim rather than generating a chart, which is usable context. However, there is no explicit when-to-use, when-not-to-use, or named alternative such as calculate_bazi_chart for the compute-from-scratch case.

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