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

bazi-solar-term-mcp

check_solar_term_boundary

Returns exact 24 Solar Term transition timestamps for a birth year and flags dates near month/year pillar boundaries, so you can verify BaZi chart pillar calculations.

Instructions

Return exact astronomical 24 Solar Term (二十四節気 / 二十四節氣) transition timestamps for a birth year and flag whether the birthday sits near a high-hallucination month or year pillar boundary (such as LiChun / 立春).

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>"
    },
    "name": "check_solar_term_boundary"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowHoursNoProximity threshold in hours to flag as high-risk boundary (default: 24).
birthDateTimeYesBirth date/time in "YYYY-MM-DD HH:mm" or "YYYY-MM-DD".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the key behavioral facts (returns exact astronomical timestamps, flags proximity against a threshold, defaults to 24 hours), but says nothing about timezone handling, precision/calendar basis, or the shape of the returned flag — notable omissions for an astronomical calculation tool.

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?

A single sentence that front-loads the primary output and appends the risk-flagging behavior; no filler. The dual-language parentheticals are useful for term matching but add some length.

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 two-parameter, read-only calculation tool with a fully documented schema and no output schema, the description covers what is computed and why the flag matters. The remaining gap — return format and timezone assumptions — is modest but real given there is no output schema to lean on.

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 coverage is 100%, so both parameters are already fully documented, establishing a baseline of 3. The description adds minor framing by tying the window to 'high-hallucination' risk and noting the birth-year scope, but adds no format or constraint detail beyond the schema.

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 verb ('Return exact astronomical 24 Solar Term transition timestamps') and a specific secondary output ('flag whether the birthday sits near a ... boundary'), so the agent knows exactly what the tool produces. It does not explicitly contrast itself with calculate_bazi_chart or audit_llm_bazi_answer, though the boundary-flagging framing hints at its niche.

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?

Usage is implied by the phrase 'high-hallucination month or year pillar boundary' — i.e., call this before trusting a chart near LiChun — but there is no explicit when-to-use, when-not-to-use, or named alternative tool. The agent must infer the workflow position from the sibling names alone.

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