Skip to main content
Glama
pinzonjulian

Stimulus Docs MCP Server

by pinzonjulian

reference-outlets

Connect controllers for component communication and coordination between different parts of your application using the Outlets API reference.

Instructions

Outlets API reference - learn how to connect controllers to each other for component communication and coordination between different parts of your application

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'reference-outlets' tool (shared with other doc tools). Reads the content of the associated markdown file ('reference/outlets.md') using readMarkdownFile and returns it as an MCP content block, or an error message if reading fails.
    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}`
            }
          ]
        };
      }
    }
  • Tool metadata and configuration: specifies the name 'reference-outlets', description, and the documentation file path 'reference/outlets.md' used by the handler.
      folder: 'reference', file: 'outlets.md',
      name: 'reference-outlets',
      description: 'Outlets API reference - learn how to connect controllers to each other for component communication and coordination between different parts of your application'
    },
  • src/index.ts:17-45 (registration)
    Registers the MCP tool 'reference-outlets' (along with other documentation tools) on the McpServer by iterating over docFiles config and calling server.tool() with the tool name, description, and handler function.
    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 readMarkdownFile that fetches the markdown content for the tool. Supports caching based on GitHub main branch commit, fetches from GitHub raw, with local 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})`);
        }
      }
    }
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 learning and communication/coordination, which suggests a read-only or informational role, but it doesn't disclose key behavioral traits such as whether it's a query, documentation retrieval, or configuration tool, nor does it cover permissions, rate limits, or side effects. This is inadequate for a tool with zero 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is moderately concise but could be more front-loaded. It combines purpose and usage in one clause, but it's not optimally structured for quick scanning. It avoids waste but lacks the crispness of higher-scoring examples.

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 (an API reference tool likely involving informational retrieval), no annotations, no output schema, and 0 parameters, the description is incomplete. It doesn't explain what the tool returns (e.g., documentation, examples, or configuration data), leaving gaps in understanding its function and output.

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 information is needed. The description doesn't add param details, which is acceptable here. Baseline is 4 for zero parameters, as the schema fully covers the input requirements.

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

Purpose2/5

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

The description states the tool is an 'API reference' for 'Outlets' and mentions connecting controllers for component communication, which gives some purpose. However, it's vague about what the tool actually does (e.g., does it retrieve, create, or explain outlets?), and it doesn't clearly distinguish from siblings like 'reference-actions' or 'reference-controllers'. It partially restates the name ('Outlets API reference'), leaning toward tautology.

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 connecting controllers in applications, but it provides no explicit guidance on when to use this tool versus alternatives like 'reference-controllers' or 'reference-actions'. There's no mention of prerequisites, exclusions, or specific contexts, leaving the agent with minimal 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