Skip to main content
Glama
Sign In
ziwei-mcp

ziwei-mcp

by xjoey1957
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

同盘人数估算

get_twins
Read-onlyIdempotent

Estimates how many people share an identical birth chart structure (same day, hour, and gender) using public birth statistics, and returns a link to an online results page.

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": {
      "date": "<date>",
      "gender": "<gender>"
    },
    "name": "get_twins"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo出生城市（中国），如「北京」「广东省/深圳」。填了且有具体时间时做真太阳时校正
dateYes出生日期 YYYY-MM-DD。calendar=lunar 时填农历年月日，如 1990-04-21
timeNo出生钟表时间 HH:MM（24 小时制）。已知具体时间时优先填这个
branchNo只知道时辰时填：0–11 或 子/丑/寅/卯/辰/巳/午/未/申/酉/戌/亥
genderYes'male' 男 或 'female' 女
lateZiNo子时出生且为晚子时（23:00–23:59）时为 true，按次日排盘
regionNo统计范围：'china' 中国（默认）或 'world' 全球
calendarNo'solar' 公历（默认）或 'lunar' 农历
ignoreDstNo1986–1991 夏令时期间，所填已是标准时间时为 true；默认自动减 1 小时
leapMonthNo农历闰月时为 true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. Beyond those, the description adds meaningful context that the annotations do not: the estimate is derived from public birth-population statistics and the response includes an online page link. It stops short of stating that the figure is a statistical approximation with inherent uncertainty.

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?

A single front-loaded sentence with no filler: the action, the precise definition of 'twin' charts, the data source, and the returned link all appear without 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?

For a 10-parameter read-only estimation tool with full schema coverage, no output schema, and safety annotations, the description supplies enough to call it correctly and to know what comes back (a count plus a link). The main omission is any caveat about the statistical accuracy of the estimate.

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%, so every parameter including time, branch, lateZi, calendar, leapMonth, and region is already documented in the schema. The description's mention of 'same day, same 时辰, same gender' mirrors a subset of the parameters but adds no new semantics such as how time and branch interact or what happens if only a branch is supplied.

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 gives a specific verb (估算/estimate) and a precise resource (the count of people sharing an identical chart structure, defined as same day, same 时辰, same gender), plus the data basis and the returned link. It is not a tautology of the name, but it does not explicitly contrast itself with siblings get_chart or get_reading_summary.

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?

There is no statement of when to choose this over get_chart or get_reading_summary, nor any prerequisites (e.g., needing the chart first, or needing a birth time to narrow the 时辰). The usage context is only implied by the tool's purpose.

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