Skip to main content
Glama

Liki — Professional AI Astrologer

xuankong_liunian

Read-onlyIdempotent

玄空流年飞星:在宅运盘上叠加指定年份,返回流年飞星盘;count=1(默认)单年,count>1 连续批量。评估阳宅某一年风水变化时调用;固定格局用 xuankong_chart,尚未起宅运盘的也先调用 xuankong_chart。

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": {
      "standard_time": "<standard_time>",
      "zuo_shan": "<zuo_shan>",
      "xiang_shan": "<xiang_shan>"
    },
    "name": "xuankong_liunian"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo连续查询年数。
zuo_shanYes坐山,二十四山 index。
xiang_shanYes朝向;必须与坐山相对。
standard_timeYes流年选择地标准时间(无 DST),RFC3339 带 offset。

Output Schema

NameRequiredDescriptionDefault
liu_nianYes领域事实序列;长度与请求 count 一致。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedOutput schema / $defs
      Added value: +{
      +  "Enum_b00fba477008276b": {
      +    "enum": [
      +      "一白贪狼",
      +      "二黑巨门",
      +      "三碧禄存",
      +      "四绿文曲",
      +      "五黄廉贞",
      +      "六白武曲",
      +      "七赤破军",
      +      "八白左辅",
      +      "九紫右弼"
      +    ],
      +    "type": "string"
      +  }
      +}
    • addedOutput schema / properties / liu_nian / items / properties / gong_wei / items / properties / xing_name / $ref
      Added value: +"#/$defs/Enum_b00fba477008276b"
    • removedOutput schema / properties / liu_nian / items / properties / gong_wei / items / properties / xing_name / enum
      Removed value: -[
      -  "一白贪狼",
      -  "二黑巨门",
      -  "三碧禄存",
      -  "四绿文曲",
      -  "五黄廉贞",
      -  "六白武曲",
      -  "七赤破军",
      -  "八白左辅",
      -  "九紫右弼"
      -]
    • removedOutput schema / properties / liu_nian / items / properties / gong_wei / items / properties / xing_name / type
      Removed value: -"string"
    • addedOutput schema / properties / liu_nian / items / properties / house_overlay / items / properties / star / $ref
      Added value: +"#/$defs/Enum_b00fba477008276b"
    • removedOutput schema / properties / liu_nian / items / properties / house_overlay / items / properties / star / enum
      Removed value: -[
      -  "一白贪狼",
      -  "二黑巨门",
      -  "三碧禄存",
      -  "四绿文曲",
      -  "五黄廉贞",
      -  "六白武曲",
      -  "七赤破军",
      -  "八白左辅",
      -  "九紫右弼"
      -]
    • removedOutput schema / properties / liu_nian / items / properties / house_overlay / items / properties / star / type
      Removed value: -"string"
    • addedOutput schema / properties / liu_nian / items / properties / ru_zhong / $ref
      Added value: +"#/$defs/Enum_b00fba477008276b"
    • removedOutput schema / properties / liu_nian / items / properties / ru_zhong / enum
      Removed value: -[
      -  "一白贪狼",
      -  "二黑巨门",
      -  "三碧禄存",
      -  "四绿文曲",
      -  "五黄廉贞",
      -  "六白武曲",
      -  "七赤破军",
      -  "八白左辅",
      -  "九紫右弼"
      -]
    • removedOutput schema / properties / liu_nian / items / properties / ru_zhong / type
      Removed value: -"string"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds real behavioral context beyond them: the operation depends on an existing base chart, and count>1 performs a consecutive batch rather than a single-year query. It does not mention limits or performance characteristics of the batch, so it is short of a 5.

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?

It is front-loaded with purpose, then count semantics, then routing guidance, in two dense clauses with no filler. Most of it earns its place; the sibling name is repeated twice in the final clause, though this is a minor redundancy.

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?

An output schema exists, so return values need not be explained. Required inputs and their constraints are fully documented in the schema, and the description covers the missing prerequisite and the default. What remains unstated is only the batch limit and behavior at the 50-year cap, which is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: the default value of count=1 is not expressed in the schema, and the description clarifies that count>1 means consecutive years. The 坐山/朝向 parameters are left to the schema, which is acceptable at full coverage.

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: overlays a given year onto the house luck chart (宅运盘) and returns the annual flying-star chart (流年飞星盘). It also explains the count semantics (single year vs. consecutive batch), and explicitly distinguishes itself from xuankong_chart, which handles fixed patterns.

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 gives explicit use conditions: 'evaluate a given year's feng shui change for a yang dwelling'. It names the alternative (xuankong_chart) for fixed charts, and states a prerequisite: if the base house luck chart has not been cast yet, call xuankong_chart first.

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