Skip to main content
Glama
pinzonjulian

Stimulus Docs MCP Server

by pinzonjulian

handbook-external

Integrate external APIs and third-party libraries using AJAX requests and asynchronous operations for Stimulus JS applications.

Instructions

Techniques for integrating external APIs and resources - covers AJAX requests, working with third-party libraries, and asynchronous operations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that reads the specific markdown file for the tool, implementing cache check, GitHub fetch with caching, and local file fallback.
    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})`);
        }
      }
    }
  • Configuration entry defining the tool name, description, folder, and file path for 'handbook-external' in the docFiles array.
      folder: 'handbook',
      file: '06_working_with_external_resources.md',
      name: 'handbook-external',
      description: 'Techniques for integrating external APIs and resources - covers AJAX requests, working with third-party libraries, and asynchronous operations'
    },
  • src/index.ts:17-45 (registration)
    Registers the 'handbook-external' tool (and all others) on the MCP server using config data, with an inline async handler that reads the file and returns markdown content or error.
    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}`
                }
              ]
            };
          }
        }
      );
    });
  • Helper function used by the handler to fetch markdown content from GitHub raw URL and cache it locally.
    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. It mentions 'techniques' and topics like AJAX requests, but doesn't disclose behavioral traits such as whether this is a read-only reference, requires authentication, has rate limits, or what output to expect. This leaves significant gaps for a tool with no structured behavioral hints.

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 lists key topics without unnecessary words. It's front-loaded with the main purpose, though it could be slightly more structured by explicitly stating the tool's function (e.g., 'Provides guidance on...').

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 complexity implied by covering multiple integration techniques, lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., documentation, examples, or code snippets) or behavioral aspects, making it inadequate for an agent to use effectively.

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 with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter details, but this is appropriate given the lack of inputs, meeting the baseline for a parameterless tool.

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 covers 'techniques for integrating external APIs and resources' with specific topics like AJAX requests and third-party libraries, which gives a general purpose. However, it doesn't specify a clear verb (e.g., 'learn', 'explain', 'guide') or distinguish itself from sibling tools like 'handbook-building' or 'handbook-resilience', making it somewhat vague.

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 lists topics covered but doesn't indicate context, prerequisites, or exclusions, leaving the agent with no usage direction.

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