Skip to main content
Glama

Get Chinese Astrology

Zi Wei Dou Shu chart

get_zi_wei_chart
Read-onlyIdempotent

Builds a Zi Wei Dou Shu chart for a birth date, a birth time and a traditional calculation table. Returns the lunar date, the Five Element bureau, the Life and Body palace branches and the major stars with their brightness and transformations in each of the twelve palaces.

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": {
      "birthDate": "<birthDate>",
      "time": "<time>",
      "gender": "<gender>"
    },
    "name": "get_zi_wei_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeYesLocal birth time as HH:MM on a 24-hour clock.
genderYesTraditional calculation table: male or female.
birthDateYesBirth date as YYYY-MM-DD, from 1900-01-01 to 2099-12-31.

Output Schema

NameRequiredDescriptionDefault
ctaNo
viewYes
chartNo
itemsYes
linksNo
titleNo
totalYes
layoutNo
requestYes
pageSizeYes
subtitleNo
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's remaining contribution is the enumeration of returned content (lunar date, Five Element bureau, palace branches, star brightness and transformations), but since an output schema exists that value is largely duplicated. Nothing is said about failure modes such as dates outside 1900-2099.

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?

Two sentences, front-loaded with the action and inputs before the return values. It is efficient overall, though the second sentence spends its length re-listing return fields that the output schema already defines.

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 three-required-parameter, non-nested, closed-world computation tool with full schema coverage, full annotations and an output schema, the description supplies enough to invoke it correctly. The only meaningful gap is the absence of any routing guidance relative to the other charting tools.

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%, so all three parameters are already documented with formats, patterns and the gender enum, which sets the baseline at 3. The description only restates the parameter set and adds the phrase 'traditional calculation table' to frame the gender input, which the schema already conveys.

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 opens with a specific verb and resource ('Builds a Zi Wei Dou Shu chart') and names the three inputs that drive it, so the agent knows exactly what the tool produces. It is distinguishable from siblings like get_bazi_chart by the explicit Zi Wei Dou Shu framing, though it never states that distinction outright.

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 when-to-use guidance at all: nothing says when a Zi Wei Dou Shu chart is preferable to get_bazi_chart, get_flying_stars, or the other charting siblings. The agent must infer the use case purely from the tool name and the domain vocabulary.

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.