Skip to main content
Glama

Fengshui Calculator

kua_number

Ming Gua (Kua number) from birth date + gender, with the Lichun year boundary computed astronomically, five-yellow substitution conventions, and eight favourable/unfavourable directions

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": {
      "gender": "<gender>"
    },
    "name": "kua_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNobirth date YYYY-MM-DD
hourNo
genderYes
minuteNo
conventionNofive-yellow substitution: standard = male Kun/female Gen; gen = both Gen

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?

With no annotations, the description carries the full burden. It does disclose meaningful behavioral traits: the Lichun year boundary is computed astronomically (not by Gregorian year), and a five-yellow substitution convention is applied — both are non-obvious and valuable. However it says nothing about how invalid dates or partial inputs are handled, nor what the returned direction set looks like structurally.

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 dense clause that front-loads the domain term and then enumerates the notable behaviors. No filler language, though it is a fragment rather than a structured sentence and slightly stacks multiple ideas without separation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter, no-annotation, no-output-schema calculation tool, the description covers the domain concept and two important computational conventions but leaves hour/minute semantics and the shape of the returned directions unspecified. Adequate as a minimum-viable definition, but not enough for an agent to call it confidently with precise time inputs.

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 only 40%, so the description must compensate. It conveys the role of date and gender and references the convention behavior (though the enum values themselves are already documented in the schema). The hour and minute parameters are unexplained in both schema and description, leaving a substantive gap for a calculation whose precision depends on date/time.

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 resource (Ming Gua / Kua number) and the inputs that produce it (birth date + gender), plus what the output contains (eight favourable/unfavourable directions). That is well beyond a tautology and clearly identifies a Feng Shui calculation distinct from siblings like flying_star_chart or ganzhi, though it never explicitly contrasts with them.

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 statement of when to reach for this tool versus siblings such as flying_star_chart or form_analysis, and no exclusions. The domain subject material implies a use case, but the description provides no routing guidance toward or away from alternatives.

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