Skip to main content
Glama
Sign In
ziwei-mcp

ziwei-mcp

by SiwuXue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

health_analysis

Identify potential health issues from your Ziwei chart and receive personalized wellness recommendations for prevention, current concerns, or long-term trends.

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>",
      "currentAge": "<currentAge>"
    },
    "name": "health_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
chartIdYes命盘ID
currentAgeYes当前年龄
analysisTypeNo分析类型prevention
healthConcernsNo健康关注点

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only states a vague purpose and gives no information about side effects, required permissions, return values, or any constraints. This is a significant gap for a tool with health-related parameters.

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

Conciseness2/5

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

The description is extremely brief (one phrase), but this is under-specification rather than effective conciseness. It lacks structure, such as separating purpose from usage details, and fails to convey necessary information.

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

Completeness1/5

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

The tool has 4 parameters, an enum with 3 analysis types, an array of health concerns, and no output schema or annotations. The description gives no context about what the health analysis entails, what advice is provided, or how the input parameters affect the result. It is completely inadequate for the tool's complexity.

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?

The schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds no parameter-specific information beyond what the schema provides. It doesn't clarify the meaning of 'chartId', 'currentAge', 'analysisType', or 'healthConcerns' beyond their literal names.

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 '健康分析和养生建议' (health analysis and wellness advice) indicates the tool's subject matter but not a specific action or scope. It is a bit tautological with the name 'health_analysis' but adds 'wellness advice.' It does not clearly distinguish it from sibling tools like 'analyze_life_timeline' or 'career_guidance.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of appropriate contexts, prerequisites, or exclusions. Sibling tools exist, but the description doesn't position this tool among them.

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