AstroWay Astrology API (full catalogue)

Generate BaZi Report (PDF or HTML)

astroway_reports_bazi

The /bazi/chart reading as an A4 PDF (default), HTML or Markdown: the four pillars with stems, branches, animals, ten gods, hidden stems, na yin and the twelve stages; the day master with its classical image; the five elements counted three ways; the strength verdict with favourable elements and its stated thresholds; the symbolic stars; the branch interactions; and the ten-year luck pillars when gender is given. Takes the /bazi/chart birth input (date, time, timezoneOffset or timezone, longitude with trueSolarTime, dayBoundary), plus name and city for the cover. No AI.

[Group: Reports] [Endpoint: POST /v1/reports/bazi] [Required: date] [Cost: 5,000 credits (Tier 7)] ⚠️ Premium — ~50% of free monthly budget. Confirm with user before invoking.

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": {
      "date": "<date>"
    },
    "name": "astroway_reports_bazi"
  }
}

Input Schema

Name	Required	Description
`city`	No	Printed on the cover; the chart is read from date, time, zone and longitude.
`date`	Yes
`name`	No	Printed on the cover.
`time`	No
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`format`	No	`pdf` (default) stores a PDF and answers with its `url`. `html` returns one self-contained `text/html` document, `markdown` returns `text/markdown` with the same sections and tables; neither is stored. Same price in every format.
`gender`	No
`language`	No
`timezone`	No	IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
`longitude`	No
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`whitelabel`	No
`dayBoundary`	No
`stageSchool`	No
`trueSolarTime`	No
`timezoneOffset`	No	Ignored when timezone is sent.

Output Schema

Name	Required	Description	Default
`url`	No
`expires_at`	No
`page_count`	No
`byte_length`	No
`duration_ms`	No
`storage_key`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 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=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is partly covered; the description adds that no AI is involved and that this is a premium 5,000-credit (Tier 7) operation needing user confirmation. It does not disclose generation latency, whether generated reports can be retrieved later (astroway_reports_history is a sibling), or the consequences of repeated non-idempotent calls that each spend credits.

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?

Front-loaded with the output formats and the source reading, followed by the section list and input summary; each clause carries information rather than filler. The long catalogue of report sections is dense but proportional to the size of the deliverable.

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?

For a 16-parameter, credit-expensive document generator with an output schema present (so return values need not be explained), the definition covers formats, pricing, the full birth input and the cover fields. The gaps are the undocumented whitelabel branding object and the language/stageSchool toggles, which the agent must infer from the schema alone.

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 44% across 16 parameters, so the description has to compensate. It handles the birth input well (date, time, timezoneOffset or timezone, longitude with trueSolarTime, dayBoundary) and adds real meaning such as gender enabling the luck pillars and name/city being cover-only. It says nothing about the large nested whitelabel object, language, stageSchool, fields or precision, leaving those undocumented in both places.

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?

States a specific verb and resource: it renders the /bazi/chart reading as an A4 PDF (default), HTML or Markdown, and enumerates exactly what the document contains (four pillars, ten gods, hidden stems, na yin, twelve stages, day master, element balance, strength verdict, symbolic stars, branch interactions, luck pillars). This cleanly separates the report-export tool from the data siblings such as astroway_bazi_chart or astroway_bazi_four_pillars.

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?

Gives concrete usage conditions: PDF is the default, gender must be supplied to get ten-year luck pillars, and the 'No AI' note plus the premium cost warning ('Confirm with user before invoking') tell the agent this is an expensive document product rather than a quick data read. What is missing is an explicit pointer to an alternative when the agent only needs the raw chart data.

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

All AstroWay Astrology API (full catalogue) 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?