Skip to main content
Glama
pinzonjulian

Stimulus Docs MCP Server

by pinzonjulian

handbook-introduction

Learn Stimulus core concepts including controllers, actions, targets, and values to enhance server-rendered HTML by separating content from behavior.

Instructions

Introduction to Stimulus core concepts: controllers, actions, targets, and values. Explains how Stimulus enhances server-rendered HTML and separates content from behavior

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the "handbook-introduction" tool. Reads the markdown file content using readMarkdownFile and returns it as MCP formatted content block with error handling.
    async () => {
      try {
        const content = await readMarkdownFile(path.join(folder, file));
        return {
          content: [
            {
              type: "text",
              text: content
            }
          ]
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return {
          content: [
            {
              type: "text",
              text: `Error reading ${file}: ${errorMessage}`
            }
          ]
        };
      }
    }
  • Configuration object defining the metadata, source file path, and description for the "handbook-introduction" tool used during registration.
    folder: 'handbook',
    file: '01_introduction.md',
    name: 'handbook-introduction',
    description: 'Introduction to Stimulus core concepts: controllers, actions, targets, and values. Explains how Stimulus enhances server-rendered HTML and separates content from behavior'
  • src/index.ts:16-45 (registration)
    Dynamic registration of all documentation MCP tools, including "handbook-introduction", by iterating over docFiles array and calling server.tool with name, description, and handler function.
    // Register a tool for each documentation file
    docFiles.forEach(({ folder, file, name, description }) => {
      server.tool(
        name,
        description,
        async () => {
          try {
            const content = await readMarkdownFile(path.join(folder, file));
            return {
              content: [
                {
                  type: "text",
                  text: content
                }
              ]
            };
          } catch (error) {
            const errorMessage = error instanceof Error ? error.message : String(error);
            return {
              content: [
                {
                  type: "text",
                  text: `Error reading ${file}: ${errorMessage}`
                }
              ]
            };
          }
        }
      );
    });
  • Core helper function that reads the markdown file ('handbook/01_introduction.md' for this tool) from cache, GitHub, or local filesystem with fallbacks.
    export async function readMarkdownFile(filename: string): Promise<string> {
      const filePath = path.join(docsFolder, filename);
      if (!filePath.startsWith(docsFolder)) {
        throw new Error("Invalid file path");
      }
      
      // Get current commit info if we don't have it yet
      if (!mainBranchInfo) {
        try {
          const commitInfo = await fetchMainBranchInformation();
          const cacheKey = `${commitInfo.sha.substring(0, 7)}-${commitInfo.timestamp}`;
          mainBranchInfo = {
            ...commitInfo,
            cacheKey
          };
        } catch (shaError) {
          console.error('Failed to get GitHub commit info, falling back to direct fetch');
        }
      }
      
      // Try to read from cache first if we have commit info
      if (mainBranchInfo) {
        const cachedFilePath = path.join(cacheFolder, mainBranchInfo.cacheKey, filename);
        try {
          const content = await fs.promises.readFile(cachedFilePath, "utf-8");
          console.error(`Using cached content for ${mainBranchInfo.cacheKey}: ${filename}`);
          return content;
        } catch (cacheError) {
          // Cache miss, continue to fetch from GitHub
        }
      }
      
      // Fetch from GitHub
      try {
        return await fetchFromGitHub(filename, mainBranchInfo?.cacheKey);
      } catch (githubError) {
        console.error(`GitHub fetch failed: ${githubError}, attempting to read from local files...`);
        
        // Fallback: read from local files
        try {
          return await fs.promises.readFile(filePath, "utf-8");
        } catch (localError) {
          const githubErrorMessage = githubError instanceof Error ? githubError.message : String(githubError);
          const localErrorMessage = localError instanceof Error ? localError.message : String(localError);
          throw new Error(`Failed to read file from GitHub (${githubErrorMessage}) and locally (${localErrorMessage})`);
        }
      }
    }
  • Helper function to fetch markdown content directly from GitHub and handle caching, invoked by readMarkdownFile.
    export async function fetchFromGitHub(filename: string, cacheKey?: string): Promise<string> {
      const githubUrl = `${GITHUB_RAW_BASE_URL}/${filename}`;
      const response = await fetch(githubUrl);
      
      if (!response.ok) {
        throw new Error(`GitHub fetch failed: ${response.status} ${response.statusText}`);
      }
      
      const content = await response.text();
      
      // Cache the content with cache key if available
      if (cacheKey) {
        try {
          const cacheFolder = path.resolve(__dirname, "../cache");
          const cachedFilePath = path.join(cacheFolder, cacheKey, filename);
          await fs.promises.mkdir(path.dirname(cachedFilePath), { recursive: true });
          await fs.promises.writeFile(cachedFilePath, content, "utf-8");
          console.error(`Cached GitHub content for ${cacheKey}: ${filename}`);
        } catch (cacheError) {
          console.error(`Failed to cache content: ${cacheError}`);
        }
      }
      
      return content;
    }
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 describes the educational content but doesn't reveal key behavioral traits: whether it's interactive, returns text/html, has side effects, requires authentication, or handles errors. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 highly concise and well-structured in a single sentence. It front-loads the core purpose (introducing Stimulus concepts) and efficiently adds explanatory context without redundancy. Every word earns its place, making it easy to scan and understand.

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 complexity (educational content with no parameters) and lack of annotations/output schema, the description is minimally complete. It states what the tool covers but doesn't address how it behaves or what users can expect. For a tool with no structured data to rely on, 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 appropriately avoids discussing parameters, focusing instead on the tool's purpose. This meets the baseline for tools without parameters, as it doesn't mislead or omit necessary information.

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: introducing Stimulus core concepts (controllers, actions, targets, values) and explaining how Stimulus enhances server-rendered HTML while separating content from behavior. It uses specific terminology and identifies the educational scope, though it doesn't explicitly differentiate from sibling tools like 'handbook-building' or 'handbook-origin' which might cover related concepts.

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., prior knowledge needed), target audience, or how it fits with sibling tools such as 'handbook-installing' or 'reference-controllers'. The user must infer usage from the title alone.

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/pinzonjulian/stimulus-docs-mcp-server'

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