Skip to main content
Glama

AstroWay Chinese metaphysics

Travel Palace (Qianyi)

astroway_ziwei_palace_travel
Read-onlyIdempotent

Travel, relocation, foreign opportunities.

[Group: Zi Wei Dou Shu (Purple Star)] [Endpoint: POST /v1/ziwei/palace-travel] [Required: date] [Cost: 5 credits (Tier ½)]

Input Schema

NameRequiredDescriptionDefault
dateYes
timeNo
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
timezoneNoIANA 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.
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
timezoneOffsetNoIgnored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
animalNo
palaceNo
solarYearNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedOutput schema / properties / animal / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / animal / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / disclaimer / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / disclaimer / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / palace / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {},
      -    "properties": {
      -      "chinese": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "english": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "key": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "pinyin": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "rules": {
      -        "anyOf": [
      -          {
      -            "items": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "type": "array"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "theme": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "chinese": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "english": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "key": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "pinyin": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "rules": {
      +        "anyOf": [
      +          {
      +            "items": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "type": "array"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "theme": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / solarYear / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / solarYear / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description's added value is operational: the endpoint (POST /v1/ziwei/palace-travel) and the cost of 5 credits (Tier ½), which annotations do not convey. It says nothing about what the palace analysis contains or how it scales with input.

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?

There is zero wasted wording and the metadata tags are consistently formatted and front-loaded. The trade-off is that brevity here comes from omission rather than compression — the core five-word fragment carries almost no informational payload.

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

Completeness3/5

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

An output schema exists and annotations are rich, so return values and safety need not be described. What is still missing is anything telling an agent what the travel-palace result means or how it differs from the twelve-palaces overview call, which leaves the definition minimally viable for a single-required-param calculation tool.

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?

At 67% schema description coverage, the schema already documents timezone, timezoneOffset, fields and precision in detail. The description only restates '[Required: date]', which duplicates the schema's required array and adds no meaning such as whether time affects the palace placement or how missing time is handled.

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

Purpose3/5

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

The description is a topic list ('Travel, relocation, foreign opportunities') with no verb or resource noun, so it never states that the tool computes or returns the Zi Wei Travel Palace (Qianyi). The topic keywords do separate it from siblings like palace_career or palace_health, but an agent must infer what the call actually does from the name and title.

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 choose this palace tool over astroway_ziwei_twelve_palaces or astroway_ziwei_full_chart, no prerequisites, and no exclusions. The only context is the '[Group: Zi Wei Dou Shu]' tag, which implies usage but does not direct selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources