Auspice BaZi — Four Pillars Chart

Personality sketch (fill-in template)

personality_sketch

Read-onlyIdempotent

Step 1 of 2 for a personality sketch. Casts the chart and returns the chart facts plus a fill-in template (象 image / 里 beneath / 行 practice) for YOU, the assistant, to write — a short literary sketch grounded only in the returned facts, within the stated limits (no strength verdict, no favorable elements, no Ten Gods, no luck-cycle reading). Step 2: pass your three texts to compose_sketch and present its framed sheet verbatim. Deterministic facts; the prose is yours; the framing is the server’s.

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": {
      "year": "<year>",
      "month": "<month>",
      "day": "<day>",
      "hour": "<hour>",
      "minute": "<minute>",
      "timeZone": "<timeZone>",
      "longitude": "<longitude>"
    },
    "name": "personality_sketch"
  }
}

Input Schema

Name	Required	Description
`day`	Yes	Birth day of month, 1–31
`hour`	Yes	Recorded wall-clock hour, 24-hour format
`lang`	No	Language of the rendered output — pass the language the user is conversing in. Defaults to 'en'.
`year`	Yes	Birth year, Gregorian calendar (engine ephemeris covers 1900–2100)
`month`	Yes	Birth month, 1–12
`minute`	Yes	Recorded wall-clock minute, 0–59
`timeZone`	Yes	IANA time zone of the birthplace, e.g. 'Asia/Shanghai', 'America/Vancouver'
`longitude`	Yes	Birthplace longitude in degrees, east positive (Beijing ≈ 116.4, Vancouver ≈ -123.1)

Output Schema

Name	Required	Description
`season`	Yes	Season of the month branch (deterministic lookup)
`pillars`	Yes
`dayMaster`	Yes
`boundaryRisk`	Yes
`fullReadingUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds significant behavioral context: the tool is deterministic ('Deterministic facts'), the prose is the assistant's responsibility, and the framing is the server's. It also discloses the return content (facts plus template) and the limits of what it does not provide.

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?

The description is detailed and somewhat long, but every sentence serves a purpose: purpose, workflow, limits, and next step. It is front-loaded with the primary purpose and clearly structured into two steps. Slightly verbose but not wasteful.

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

Completeness5/5

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

Given the tool's complexity (8 params, output schema, sibling tool), the description is complete. It tells the agent exactly what to do, what to expect, how to proceed to step 2, and what constraints apply. Nothing essential is missing for an agent to call it correctly.

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% – every parameter has a description in the schema, so the baseline for parameter semantics is 3. The tool description does not add parameter-specific information beyond that, but it doesn't need to since the schema is comprehensive and includes ranges and examples.

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 clearly states the tool's specific role: 'Step 1 of 2 for a personality sketch' that casts the chart and returns facts plus a fill-in template. It distinguishes itself from sibling compose_sketch by naming it as step 2 and specifying the task division (deterministic facts vs. assistant's prose).

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

Usage Guidelines5/5

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

It explicitly describes the workflow: cast the chart, receive facts/template, write three texts, then pass them to compose_sketch. It also specifies what not to do (no strength verdict, no favorable elements, no Ten Gods, no luck-cycle reading), giving clear boundaries.

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

All Auspice BaZi — Four Pillars Chart 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?