Skip to main content
Glama
leejersey

Hexo Blog MCP Server

by leejersey

git_status

Check uncommitted changes in your Hexo blog project to monitor Git status before publishing updates.

Instructions

查看博客项目当前的 Git 状态(未提交的更改)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The function that actually executes `git status --short` and returns the output.
    export async function getGitStatus(): Promise<string> {
        return runCommand("git status --short");
    }
  • The registration of the 'git_status' tool using the MCP server, including the handler wrapper.
    server.tool(
        "git_status",
        "查看博客项目当前的 Git 状态(未提交的更改)",
        {},
        async () => {
            try {
                const status = await getGitStatus();
                return {
                    content: [
                        {
                            type: "text" as const,
                            text: status
                                ? `当前有未提交的更改:\n\n${status}`
                                : "✅ 工作区干净,没有未提交的更改。",
                        },
                    ],
                };
            } catch (e: any) {
                return { content: [{ type: "text" as const, text: `错误: ${e.message}` }], isError: true };
            }
        }
    );
Behavior2/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 behavioral disclosure. It states the tool views Git status for uncommitted changes, implying a read-only operation, but doesn't specify whether it requires Git installation, authentication, or network access, or describe the output format (e.g., text summary). This leaves gaps for a tool with no annotation coverage.

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

Conciseness4/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 purpose without unnecessary words. It's front-loaded with the core action ('view Git status') and includes clarifying scope ('blog project') and detail ('uncommitted changes'). However, it could be slightly more structured by separating scope from action for clarity.

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 the tool's low complexity (0 parameters, no annotations, no output schema), the description is minimally adequate. It covers the basic purpose but lacks details on behavioral traits (e.g., output format, dependencies) and usage guidelines. For a simple read tool, this is acceptable but leaves room for improvement in 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 tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids mentioning any. A baseline score of 4 is given since no parameters exist, and the description doesn't mislead about inputs.

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's purpose: '查看博客项目当前的 Git 状态(未提交的更改)' translates to 'View the current Git status (uncommitted changes) of the blog project.' It specifies the verb ('view'), resource ('Git status'), and scope ('blog project'), but doesn't explicitly differentiate from sibling tools like 'deploy_blog' or 'backup_source' that might also involve Git operations.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a Git repository), exclusions (e.g., not for committed changes), or related tools like 'deploy_blog' that might depend on Git status. Usage is implied only by the purpose, with no explicit context.

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