Skip to main content
Glama
weicizhou

悦流 Website Audit MCP

by weicizhou
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Server Quality Checklist

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

  • Latest release: v0.1.0

  • Disambiguation5/5

    The two tools have clearly distinct purposes: one checks specific search-related files (robots.txt, sitemap.xml, llms.txt) while the other performs a broader crawl and audit of pages. There is no overlap or ambiguity in their intended use.

    Naming Consistency5/5

    Both tool names follow the same verb_noun pattern (check_search_files, audit_website), using underscore separators consistently. The naming is uniform and predictable.

    Tool Count3/5

    With only two tools, the server is at the thin end of the spectrum for a website audit toolset. While the two tools cover distinct aspects, the count feels minimal and could benefit from additional tools for a more complete audit experience.

    Completeness3/5

    The toolset covers basic search file checks and on-page crawling, but there are notable missing features such as performance analysis, security headers checks, or detailed schema validation. Agents may find gaps when attempting a thorough website audit.

  • Average 4.1/5 across 2 of 2 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?

    Annotations already establish the tool is read-only and non-destructive. The description adds useful context by stating that no AI model or paid API is used, and clarifies the scope ('availability and basic validity'), providing value beyond the annotations without contradicting them.

    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 two concise sentences, front-loaded with the action and resources. Every word earns its place, with no redundancy or filler.

    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?

    Given the tool's simplicity (one parameter, read-only, no output schema), the description adequately covers the core behavior. It mentions what is checked (availability and basic validity), though it does not detail return values or edge cases, which is acceptable for this low 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 already provides a clear description for the only parameter ('Website URL, for example https://example.com'), achieving 100% coverage. The tool description does not need to add more, and it doesn't, so it meets the baseline for schema-covered parameters.

    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 uses a specific verb ('Check') and names concrete resources ('robots.txt, sitemap.xml and llms.txt') with a clear scope ('availability and basic validity'). This clearly distinguishes it from the sibling tool 'audit_website' by focusing on search discovery files.

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

    Usage Guidelines3/5

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

    The description implies a use case: checking the availability and validity of specific search discovery files. However, it does not explicitly state when to use this tool versus the sibling 'audit_website', nor does it provide any exclusions or alternatives.

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

  • Behavior4/5

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

    Annotations already declare readOnlyHint and destructiveHint:false. The description adds useful context beyond this: the crawl limit ('up to 20'), the tool's scope ('basic' issues), and notably that 'No AI model or paid API is used', which sets expectations about cost and method. No contradiction with annotations.

    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, well-structured sentence that starts with the action verb and includes all necessary high-level information. No wasted words, and the structure front-loads the core purpose.

    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?

    Given the tool has no output schema, the description, while noting the output type ('report basic SEO and AI-search readiness issues'), could be more explicit about the format or nature of the report. However, it adequately covers scope, limitations, and the fact that it's a read-only audit, which is sufficient for a tool of this simplicity.

    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 coverage is 100%, with both parameters (url and max_pages) clearly described in the schema. The description adds no new parameter-specific meaning, merely restating the limit ('up to 20') that is already in the schema. Hence baseline 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 uses a specific verb 'Crawl' with a clear resource ('same-site pages') and outcome ('report basic SEO and AI-search readiness issues'). It clearly differentiates from the sibling tool check_search_files, which is about searching files, making the tool's purpose unmistakable.

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

    Usage Guidelines4/5

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

    The description provides clear context for use: auditing up to 20 same-site pages for SEO and AI-search readiness, with a note that no paid API is used. However, it does not explicitly contrast with alternatives (like check_search_files) or state when not to use it, so it falls short of a 5.

    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

yueliu-mcp MCP server

Copy to your README.md:

Score Badge

yueliu-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/weicizhou/yueliu-mcp'

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