Skip to main content
Glama

Mingpath

ziwei_chart

Compute a Zi Wei Dou Shu (紫微斗数) chart: twelve palaces with major/minor stars, brightness and birth-year transformations (四化), five-element bureau, soul/body stars. Uses the same 子时 convention as bazi_chart. Needs the birth hour. Free.

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": {
      "year": "<year>",
      "month": "<month>",
      "day": "<day>",
      "hour": "<hour>"
    },
    "name": "ziwei_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNoIANA time zone of the birthplace, e.g. Asia/Shanghai, America/Los_Angeles. Preferred over tz_hours: historical summer time is applied (the mainland observed it 1986–1991, Hong Kong and Taiwan in many earlier years), so a clock time read off a birth certificate in summer time gives the right hour pillar
dayYes
hourYes0-23 local clock hour; omit if unknown
yearYes
monthYes
genderNo
minuteNo
zi_ruleNo子时 convention: 1 = a birth after 23:00 counts as the next day; 2 (default) = same day
tz_hoursNofixed UTC offset of the birthplace in hours, e.g. 8 (no summer time); used only when tz is absent
longitudeNobirthplace longitude in degrees east, e.g. 103.82 for Singapore

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the returned components, which compensates for the absent output schema, states the hour requirement, notes the 子时 convention parity with bazi_chart, and discloses cost ('Free'). It does not explain error behavior when the hour is unknown or how time-zone resolution affects the palaces, leaving a modest gap for a computation tool with no annotations.

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?

Four short sentences, front-loaded with the output inventory and then the key requirements and convention note. Nothing is wasted apart from the bare 'Free.' tag, which arguably earns its place as cost disclosure but reads as marketing.

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 ten-parameter computation tool without annotations or an output schema, the description successfully replaces the missing output schema by listing chart components and carries the critical hour requirement. The remaining gap is parameter-level detail on gender, time zone and longitude handling, which is partially but not fully covered by the schema.

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?

Schema description coverage is 50% on ten parameters, so the description must compensate, yet it only reinforces 'hour' and alludes to zi_rule via the 子时 parity note. Gender, minute, longitude, tz and tz_hours get no explanation in the description, so half the parameters remain thin in both places.

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?

A specific verb (compute) plus a named resource (Zi Wei Dou Shu chart), followed by an enumeration of what the chart contains: twelve palaces, major/minor stars, brightness, 四化, five-element bureau, soul/body stars. This is concrete enough that an agent can distinguish it from bazi_chart, a different astrological system, without opening either schema.

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 rather than stated: the description establishes this is the Zi Wei Dou Shu tool and that it 'needs the birth hour,' so the precondition is clear. However, it never says when to prefer this over bazi_chart or other siblings, and it gives no exclusions or fallback behavior.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources