Skip to main content
Glama
ThaLoc0one

Documentation MCP Server

by ThaLoc0one

docs_build_static

Build static documentation websites from Docusaurus, MkDocs, or Sphinx projects for deployment to GitHub Pages, Netlify, or Vercel.

Instructions

Build static website for online hosting (ready for GitHub Pages, Netlify, Vercel, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
docsPathYesPath to documentation directory
frameworkYesDocumentation framework used
outputPathNoOutput path for built site (default: ./build)

Implementation Reference

  • The buildStatic function that executes the tool logic for building static documentation sites. Returns step-by-step instructions for building and deploying Docusaurus, MkDocs, or Sphinx sites.
    export async function buildStatic(args: any) {
      const { docsPath, framework, outputPath } = args as BuildStaticArgs;
    
      const instructions: Record<string, string> = {
        docusaurus: `🏗️ Building Docusaurus Static Site:
    
    1. Navigate to docs directory:
       cd ${docsPath}
    
    2. Install dependencies (if not done):
       npm install
    
    3. Build:
       npm run build
    
    4. Output location: ${docsPath}/build
    
    5. Test the build locally:
       npm run serve
    
    6. Deploy to:
       - GitHub Pages: npm run deploy
       - Netlify: Drag & drop the 'build' folder
       - Vercel: Connect your repo`,
        mkdocs: `🏗️ Building MkDocs Static Site:
    
    1. Navigate to project directory:
       cd ${docsPath}
    
    2. Build:
       mkdocs build
    
    3. Output location: ${docsPath}/site
    
    4. Preview:
       cd site && python -m http.server 8000
    
    5. Deploy to GitHub Pages:
       mkdocs gh-deploy`,
        sphinx: `🏗️ Building Sphinx Static Site:
    
    1. Navigate to docs directory:
       cd ${docsPath}
    
    2. Build HTML:
       make html
    
    3. Output location: ${docsPath}/_build/html
    
    4. Preview:
       cd _build/html && python -m http.server 8000
    
    5. For ReadTheDocs: Connect your repository at readthedocs.org`,
      };
    
      const instruction = instructions[framework] || "Framework not supported";
    
      return {
        content: [
          {
            type: "text",
            text: instruction,
          },
        ],
      };
    }
  • TypeScript interface BuildStaticArgs defining input parameters: docsPath (required), framework (required), and outputPath (optional).
    interface BuildStaticArgs {
      docsPath: string;
      framework: string;
      outputPath?: string;
    }
  • src/index.ts:133-155 (registration)
    Registration of the 'docs_build_static' tool in the tools array, including its description and inputSchema (with docsPath, framework enum [docusaurus, mkdocs, sphinx], and outputPath).
    {
      name: "docs_build_static",
      description: "Build static website for online hosting (ready for GitHub Pages, Netlify, Vercel, etc.)",
      inputSchema: {
        type: "object",
        properties: {
          docsPath: {
            type: "string",
            description: "Path to documentation directory",
          },
          framework: {
            type: "string",
            description: "Documentation framework used",
            enum: ["docusaurus", "mkdocs", "sphinx"],
          },
          outputPath: {
            type: "string",
            description: "Output path for built site (default: ./build)",
          },
        },
        required: ["docsPath", "framework"],
      },
    },
  • Case statement in the CallToolRequestSchema handler that routes 'docs_build_static' to the buildStatic function.
    case "docs_build_static":
      return await buildStatic(args);
  • Import of the buildStatic function from ./tools/buildStatic.js.
    import { buildStatic } from "./tools/buildStatic.js";
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention that the tool generates files in the output path, may overwrite existing files, or requires an existing documentation directory and installed framework. The description is too vague about side effects.

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, concise sentence that front-loads the core action and purpose. No unnecessary words or repetition.

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?

Given the lack of annotations and output schema, the description should provide more context about execution (e.g., that output is written to disk, that docsPath must contain a valid project, that framework must be installed). It currently leaves many operational details unstated.

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 input schema covers all three parameters with clear descriptions (100% coverage). The tool description adds no extra parameter information, so baseline score of 3 is appropriate—it neither enhances nor detracts from the schema.

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's purpose: build a static website for online hosting. It uses a specific verb ('Build') and resource ('static website'), and distinguishes itself from sibling tools like docs_preview (local preview) and docs_export_pdf (PDF export).

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 usage for deployment to platforms like GitHub Pages, Netlify, Vercel, but does not explicitly state when not to use it or mention alternatives like docs_preview for local testing. Guidance is present but not fully explicit.

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/ThaLoc0one/documentation-mcp-server'

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