Skip to main content
Glama
Sign In
ziwei-mcp

ziwei-mcp

by SiwuXue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

analyze_life_timeline

Analyze life timeline from a Ziwei chart, detailing major luck periods and annual fortunes over a specified age range. Select granularity from decade, year, or month for precise insights.

Instructions

分析人生时间轴，包括大运流年详细分析

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": {
      "chartId": "<chartId>",
      "startAge": "<startAge>",
      "endAge": "<endAge>"
    },
    "name": "analyze_life_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
endAgeYes结束年龄
chartIdYes命盘ID
startAgeYes起始年龄
analysisGranularityNo分析粒度year

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure, but it does not mention whether the operation is read-only, what output format to expect, or any limitations. It only names the analysis scope, which is insufficient for an un-annotated tool.

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?

The description is a single sentence, front-loaded with the primary verb and resource, and followed by a specific detail about the analysis content. There is no wasted wording or redundancy.

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?

There is no output schema and no annotations, so the description should clarify what the analysis returns and how to interpret it, but it does not. The schema covers parameter meanings, but tool-level context such as usage scenarios, return values, and behavioral expectations is missing.

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 description coverage is 100% — all four parameters (chartId, startAge, endAge, analysisGranularity) have concise descriptions. The tool description adds no parameter-level information beyond what the schema already provides, so the baseline score of 3 is appropriate.

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?

The description clearly states the tool analyzes a life timeline ('分析人生时间轴') and specifies the analysis scope as major-period and annual fortune ('大运流年详细分析'). This specific verb+resource combination distinguishes it from siblings like analyze_fortune.

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 given about when to use this tool versus alternatives, no exclusions, and no mention of prerequisites. The description only states what the tool does, leaving the agent to infer usage from the name.

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

Deploy Server

Other Tools