Snuug room calculators

Bagua map for a room

bagua_map

Read-onlyIdempotent

Use when someone asks how to use a feng shui bagua map in a room or a home, which area of a room is wealth or relationships, or where their door falls on the bagua. It reports what the tradition says; feng shui is a tradition, not a science.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bagua_map"
  }
}

Input Schema

Name	Required	Description	Default
`facing`	No	For the compass method: the way you face as you walk in, N, NE, E, SE, S, SW, W or NW.	N
`method`	No	btb (from the door, the Western school) or compass.	btb
`door_wall`	No	The wall the door is on, as drawn on the plan: bottom, left, top or right.	bottom
`door_position`	No	Where the door is on that wall, standing in the doorway looking in: left, middle or right.	middle
`room_width_cm`	No	The room’s width, across the plan (cm).
`room_length_cm`	No	The room’s length, up the plan (cm).

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.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one genuine piece of non-structured context, the caveat that feng shui is a tradition and not a science, which frames how the agent should present results. It says nothing about how the two methods differ in output or what the returned map looks like.

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 tight sentences: usage triggers first, epistemic caveat second. No filler, no repetition of schema fields, and the most decision-relevant information is front-loaded.

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?

An output schema exists, so return values need no explanation, and all six parameters are fully described structurally. For a read-only calculation tool the coverage is close to complete; the only shortfall is that the btb-versus-compass choice, the one decision an agent might have to make on the user's behalf, is left entirely to the schema.

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% and every parameter including the btb/compass method and door placement is documented in the schema itself. The description adds no interpretation of method choice or how facing/door_wall interact. Baseline 3 applies since the schema carries the full load.

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 the resource precisely (a feng shui bagua map for a room or home) and specifies the kinds of answers it produces (which area is wealth or relationships, where the door falls). It is clearly distinct from the sizing/lighting siblings. It stops short of a crisp verb-plus-object statement of what the tool returns, relying on example questions instead.

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?

It gives three concrete trigger questions (how to use the map, which area maps to wealth/relationships, where the door falls), which is strong when-to-use guidance. No exclusion or alternative is named, though the sibling set covers unrelated domains so the risk of misrouting is low.

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?