Skip to main content
Glama
pinzonjulian

Stimulus Docs MCP Server

by pinzonjulian

handbook-state

Understand how Stimulus manages state using values and data attributes. Learn reactive programming patterns to keep state synchronized with the DOM.

Instructions

Learn how Stimulus manages state through values and data attributes - covers reactive programming patterns and keeping state in sync with the DOM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/config.ts:46-50 (registration)
    Configuration entry that defines the 'handbook-state' tool name, associated markdown file path, and description used during tool registration.
      folder: 'handbook',
      file: '05_managing_state.md',
      name: 'handbook-state',
      description: 'Learn how Stimulus manages state through values and data attributes - covers reactive programming patterns and keeping state in sync with the DOM'
    },
  • src/index.ts:17-45 (registration)
    Registers the 'handbook-state' tool (and all other doc tools) by iterating over docFiles config and calling server.tool() with the name, description, and a handler that reads the corresponding markdown 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}`
                }
              ]
            };
          }
        }
      );
    });
  • Handler logic delegated by the tool handler: reads the markdown file content from cache, GitHub, or local fallback with commit-aware caching.
    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 current main branch commit SHA and timestamp for cache key generation.
    export async function fetchMainBranchInformation(): Promise<{sha: string, timestamp: number}> {
      try {
        const response = await fetch(`${GITHUB_API_BASE_URL}/commits/${MAIN_BRANCH}`);
        if (!response.ok) {
          throw new Error(`GitHub API failed: ${response.status} ${response.statusText}`);
        }
        const data = await response.json();
        
        // Get the commit timestamp (author date)
        const commitTimestamp = new Date(data.commit.author.date).getTime();
        
        return {
          sha: data.sha,
          timestamp: commitTimestamp
        };
      } catch (error) {
        console.error('Failed to get GitHub SHA:', error);
        throw error;
      }
    }
  • Helper function to fetch markdown file content from GitHub raw URL and optionally cache it.
    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 topic covered but doesn't reveal how the tool behaves: e.g., whether it returns text, displays a webpage, requires authentication, has side effects, or handles errors. For a tool with zero annotation coverage, this is a significant gap in transparency about its operational traits.

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 that clearly states the topic without unnecessary words. It is front-loaded with the core purpose ('Learn how Stimulus manages state'), making it easy to scan. However, it could be slightly more structured by explicitly stating the tool's action (e.g., 'Access documentation on...') to improve 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 has no parameters, no annotations, and no output schema, the description provides basic topic coverage but is incomplete for effective use. It doesn't explain what the tool returns (e.g., text, links, or interactive content) or any behavioral constraints, which is inadequate for a tool that might involve content delivery. However, the simplicity of zero parameters mitigates some complexity.

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 compensate for any gaps, and it appropriately doesn't mention parameters. A baseline of 4 is applied as per the rules for zero parameters, since no parameter information is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool provides educational content about 'how Stimulus manages state through values and data attributes' with coverage of 'reactive programming patterns and keeping state in sync with the DOM.' This gives a general purpose but lacks specificity about what action the tool performs (e.g., 'read documentation' or 'display tutorial') and doesn't clearly distinguish it from sibling tools like 'handbook-introduction' or 'reference-values' that 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 implies usage for learning about state management in Stimulus, but provides no explicit guidance on when to use this tool versus alternatives like 'handbook-introduction' for basics or 'reference-values' for specific technical details. There are no exclusions, prerequisites, or comparisons mentioned, leaving the agent to infer context from the tool name 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