Skip to main content
Glama
astroway

astroway-mcp

Official

Health Palace (Jie\'e)

ziwei_palace_health
Read-onlyIdempotent

Evaluate health, illness, and weak points in your Zi Wei Dou Shu chart using birth date to identify physical vulnerabilities.

Instructions

Body, illness, weak points.

[Group: Zi Wei Dou Shu (Purple Star) — MVP]

Example request body: {"date":"1990-06-15"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate YYYY-MM-DD
latitudeNoLatitude (some date-only endpoints accept location)
longitudeNoLongitude
timezoneOffsetNoUTC offset in hours
Behavior3/5

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

Annotations (readOnlyHint, idempotentHint, destructiveHint) already declare safety. The description adds 'Body, illness, weak points' but no behavioral details beyond that. Since annotations cover the key traits, the description adds minimal extra value.

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?

Three lines with a clear purpose, group label, and example. Every sentence is necessary and front-loaded. No waste.

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

Completeness2/5

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

No output schema, and the description does not hint at what the tool returns (e.g., text analysis, structured data). For a tool focused on health in an esoteric system, missing output expectations reduces completeness.

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% with parameter descriptions. The description adds an example request body showing date format, which is helpful but doesn't add meaning beyond the schema. Baseline 3 is appropriate.

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 'Body, illness, weak points' clearly indicates the tool covers health topics within Zi Wei Dou Shu. It distinguishes from sibling palace tools (e.g., career, wealth) by its health focus. However, it could explicitly state it returns an analysis of the health palace.

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?

No guidance on when to use this tool versus alternatives. With many sibling palace tools and generic ziwei tools, the absence of usage context or exclusion criteria makes it hard for an agent to select it appropriately.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/astroway/astroway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server