Skip to main content
Glama
astroway

astroway-mcp

Official

Siblings Palace (Xiongdi)

ziwei_palace_siblings
Read-onlyIdempotent

Assess sibling and peer relationship dynamics in Zi Wei Dou Shu using birth date and optional location.

Instructions

Brothers, sisters, peer relationships.

[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
Behavior2/5

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

The description adds no behavioral context beyond what annotations already provide. Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the tool is safe, but the description does not mention any additional traits like how parameters affect the result or what the output contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short, which is concise, but it lacks a proper sentence structure. It opens with a one-line concept, then a group label and example. It is acceptable but sacrifices completeness for brevity.

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?

With no output schema and many sibling tools, the description is incomplete. It does not describe what the tool returns or how to interpret results. Annotations provide safety but not functional context. The agent has insufficient information to use the tool effectively.

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?

Input schema has 100% coverage, so the baseline is 3. The description adds no parameter information beyond the schema, but it does include an example with date. While not enriching, it is adequate given full schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Brothers, sisters, peer relationships' is vague and does not clearly state what the tool does. It provides no verb or action, leaving the agent to infer that it retrieves Siblings Palace information for a Zi Wei Dou Shu chart. The title and group label help but the description itself is insufficient.

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 is provided on when to use this tool versus alternatives. There are many other ziwei_palace_* tools (career, children, etc.), but the description does not differentiate or offer usage context. The agent must rely solely on the name.

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