Skip to main content
Glama
leejersey

Hexo Blog MCP Server

by leejersey

stop_preview

Stop the local preview server for a Hexo blog to free system resources or prepare for deployment.

Instructions

停止正在运行的 Hexo 本地预览服务器

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the stop_preview tool which kills the preview process.
    server.tool(
        "stop_preview",
        "停止正在运行的 Hexo 本地预览服务器",
        {},
        async () => {
            if (previewProcess) {
                previewProcess.kill();
                previewProcess = null;
                return {
                    content: [{ type: "text" as const, text: "✅ 预览服务器已停止。" }],
                };
            }
            return {
                content: [{ type: "text" as const, text: "ℹ️ 当前没有正在运行的预览服务器。" }],
            };
        }
    );
  • Registration of the stop_preview tool within the McpServer.
    server.tool(
        "stop_preview",
        "停止正在运行的 Hexo 本地预览服务器",
        {},
        async () => {
            if (previewProcess) {
                previewProcess.kill();
                previewProcess = null;
                return {
                    content: [{ type: "text" as const, text: "✅ 预览服务器已停止。" }],
                };
            }
            return {
                content: [{ type: "text" as const, text: "ℹ️ 当前没有正在运行的预览服务器。" }],
            };
        }
    );
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states the tool stops a running server, implying a destructive action, but doesn't detail effects (e.g., if it terminates processes, frees ports, or affects unsaved data). It adds basic context but lacks depth on behavior like error handling or prerequisites.

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, efficient sentence in Chinese that directly states the tool's function. It's front-loaded with the core action and resource, with zero wasted words or redundancy.

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

Completeness3/5

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

Given no annotations, no output schema, and a simple 0-parameter tool, the description is minimally adequate. It covers the basic purpose but lacks details on what 'stopping' entails operationally, potential side effects, or confirmation of success. For a destructive tool, more behavioral context would improve completeness.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't mention parameters, which is appropriate. Baseline is 4 for 0 params, as it avoids unnecessary detail.

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 specific action ('停止' meaning 'stop') and the target resource ('Hexo 本地预览服务器' meaning 'Hexo local preview server'). It distinguishes from siblings like 'preview_blog' (which likely starts the server) and 'deploy_blog' (which publishes).

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 implies usage context—when a Hexo preview server is running—but doesn't explicitly state when NOT to use it or name alternatives. It's clear you'd use this after 'preview_blog', but lacks explicit exclusions or sibling comparisons.

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

Install Server

Other Tools

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/leejersey/hexo-mcp-server'

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