Skip to main content
Glama
Sign In
ziwei-mcp

ziwei-mcp

by SiwuXue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

interpret_chart

Interpret a Ziwei Doushu chart to gain detailed insights into personality, career, wealth, relationships, and health. Specify focus areas for targeted analysis.

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

Input Schema

NameRequiredDescriptionDefault
chartIdYes命盘ID（由generate_chart返回）
focusAreasNo重点分析的领域

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description must carry the burden of behavioral disclosure. It fails to mention that the tool is read-only, what output format to expect, or any side effects. It simply restates the high-level purpose without deeper behavioral context.

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 core purpose, and contains no filler. Every word contributes to stating what the tool does.

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?

The description is minimal for a complex interpretation tool. It does not explain the output format, the role of focusAreas, or how it differs from sibling tools. With no annotations and no output schema, the description leaves the agent without enough context to use the tool effectively.

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 description coverage is 100%, with both chartId and focusAreas having meaningful descriptions. The tool description adds no extra parameter details, so the baseline of 3 is appropriate.

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 clearly states the tool interprets a Zi Wei Dou Shu chart and provides personality, career, and wealth analysis. However, it does not differentiate from sibling tools like intelligent_interpretation or analyze_life_timeline, so it's clear but lacks sibling distinction.

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 provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or comparison with similar analysis tools among the siblings.

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