Skip to main content
Glama
leleshen2009

yixiangqiankun-mcp

by leleshen2009
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Server Quality Checklist

67%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • Disambiguation5/5

    With only one tool, there is absolutely no ambiguity or risk of confusing it with other tools. The agent can always uniquely select this tool for divination tasks.

    Naming Consistency5/5

    There is only one tool, so naming is trivially consistent. The name 'liuyao_divination' clearly indicates its purpose and follows a single convention.

    Tool Count3/5

    The server has only 1 tool, which is on the low end for a potentially rich domain like divination. While it may suffice for basic needs, a typical agent might expect additional tools for different divination methods or result management.

    Completeness4/5

    The single tool covers the core divination workflow (arrangement and interpretation) with parameters for question, method, gender, and manual inputs. Minor gaps like history or advanced configurations are absent but not critical.

  • Average 4.8/5 across 1 of 1 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 4 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior4/5

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

    No annotations are provided, so the description must disclose all behavioral traits. It explains the divination method (auto/manual), the need for gender in some cases, and the input format. However, it does not explicitly state that the tool is read-only or free of side effects, though it is implied by nature. Slight omission keeps it from a perfect score.

    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 well-organized with sections for purpose, trigger conditions, non-applicable scenarios, and parameter details. It is front-loaded with the core purpose and uses concise, informative sentences without redundancy.

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

    Completeness5/5

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

    Given the tool has 6 parameters with full schema coverage and no output schema, the description provides complete guidance on invocation, including conditional rules (gender for love). It covers all necessary context for correct use.

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

    Parameters5/5

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

    The input schema covers all 6 parameters with descriptions in Chinese. The description further elaborates on parameter usage, such as 'gender' being required for love topics, 'method' defaulting to auto, and the meaning of 'lines' and 'old_lines'. This adds significant value beyond the schema alone.

    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 is for Liu Yao divination using specific systems (Huozhulin method and Zengshan Buyi). It provides a concise summary of its function, distinguishing it from potential sibling tools (though none listed). The verb '排盘' and '解读' accurately describe the action.

    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?

    The description includes explicit trigger conditions (e.g., keywords like '测', '算', '卦') and non-applicable scenarios (e.g., scientific predictions). It also provides a specific rule for asking gender on love-related questions. This gives clear guidance on when to invoke the tool versus alternatives.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

yixiangqiankun-mcp MCP server

Copy to your README.md:

Score Badge

yixiangqiankun-mcp MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leleshen2009/yixiangqiankun-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server