Snuug room calculators

Kua number calculator

kua_number

Read-onlyIdempotent

Use when someone asks for their feng shui kua number, East or West group, or favourable directions from a birth date. It reports what the Eight Mansions school says; feng shui is a tradition, not a science.

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

Input Schema

Name	Required	Description	Default
`formula`	No	both, female or male: the tradition has one formula for each sex at birth.	both
`birth_date`	Yes	The birth date, YYYY-MM-DD, from 1901 to 2099.
`birth_time`	No	Optional: the local birth time, HH:MM. It matters only on the day of Li Chun (about 4 February).
`utc_offset_minutes`	No	The birth place’s offset from UTC in early February, in minutes (0 for the UK, 480 for China) (minutes).

Output Schema

Name	Required	Description
`tool`	Yes	The tool, as named in its API and page URLs.
`notes`	Yes	Caveats to pass on with the answer.
`snuug`	Yes	One line about Snuug, the app behind the calculators.
`answer`	Yes	The answer as named values.
`inputs`	Yes	Every input as the tool used it: given, a default, or filled in from the rules.
`sources`	Yes	The sources of the rules used. Every rule cites its source, with the date it was checked.
`summary`	Yes	The answer in one sentence to quote.
`version`	Yes	The version of this contract.
`working`	Yes	How the answer was worked out, one step a line.
`page_url`	Yes	The calculator on snuug.app with these inputs filled in.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.9/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 safety and side-effect behavior need no restating. The description adds one genuinely new piece of context — that results reflect the Eight Mansions school and that feng shui is a tradition, not a science — which frames how the agent should present the output. It stops short of describing result interpretation or the sex-based formula choice.

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, zero filler, with the trigger condition front-loaded and the interpretive caveat trailing. Tightly sized for the tool's simplicity.

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 and 4 fully described parameters, the description need not explain return values or parameter mechanics. It covers the trigger and the interpretive framing; the only minor gap is that it never hints at which inputs (birth_time, utc_offset_minutes) matter around Li Chun — though the schema handles that.

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% and each parameter is well documented (birth_date range, formula enum tied to sex at birth, birth_time relevance only on Li Chun, utc_offset_minutes). The description adds only 'from a birth date', so the schema is doing essentially all the work — baseline 3.

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 names the exact resource (feng shui kua number) and enumerates the concrete outputs — East/West group and favourable directions — derived from a birth date. That is enough to distinguish it from every sizing sibling (rug_size, tv_height_distance, etc.), which are physical-dimension calculators.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The leading 'Use when someone asks for...' clause gives an explicit triggering condition tied to user intent. There is no when-not guidance or named alternative, but the sibling set contains no overlapping tool, so the omission is low-risk.

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

All Snuug room calculators tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?