Skip to main content
Glama

Get Chinese Astrology

Kua number

get_kua_number
Read-onlyIdempotent

Returns the feng shui Kua number for a birth date and calculation table: its trigram, element, East or West group, and the four favourable and four unfavourable directions. Birthdays before Chinese New Year use the preceding Chinese year.

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

Input Schema

NameRequiredDescriptionDefault
formulaYesCalculation table: male or female.
birthDateYesBirth date as YYYY-MM-DD, from 1901-02-19 to 2099-12-31.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value by disclosing the Chinese New Year boundary rule ('Birthdays before Chinese New Year use the preceding Chinese year'), which an agent could not derive from any structured field and which materially affects result interpretation.

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?

Two compact sentences with no filler: the core action and return fields come first, followed by the single edge case that matters. The colon-delimited field list is an efficient way to enumerate outputs without bloating the text.

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?

With an output schema present, the description need not explain return values, yet it briefly does so anyway, and it covers the only subtle input case (Chinese New Year cutoff). Nothing essential is missing, though it never scopes the tool against the many sibling chart tools, which is the remaining contextual gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum already defines formula as male/female, so the schema does most of the work. The description nonetheless adds meaning beyond the schema by framing formula as the 'calculation table' and by supplying the birthDate edge-case rule, which is the one ambiguity an agent might otherwise get wrong.

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?

The description opens with a specific verb and resource ('Returns the feng shui Kua number') and immediately enumerates the returned attributes (trigram, element, East/West group, eight directions). This clearly separates it from sibling chart and divination tools such as get_bazi_chart or get_zi_wei_chart, so an agent can select it without opening any 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 only implied: an agent can infer this is the tool for a Kua/feng shui number lookup, but the description never states when to prefer it over the other chart tools or any prerequisites. There is no explicit when-to-use or when-not guidance, and no alternatives are named.

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