Skip to main content
Glama
pinzonjulian

Turbo Docs MCP Server

by pinzonjulian

handbook-frames

Decompose web pages into independent segments for scoped navigation, lazy loading, and cache optimization using Turbo Frames.

Instructions

Turbo Frames for page decomposition - covers independent page segments, scoped navigation, eager/lazy loading, cache benefits, targeting navigation, frame promotion to visits, and custom rendering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:16-45 (registration)
    Registers all documentation tools, including 'handbook-frames', using server.tool() with an inline handler that reads the specific markdown file and returns it as text content block.
    // 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 handler logic invoked by the tool: reads the markdown file 'handbook/04_frames.md' from cache, GitHub, or local fallback, returning the content as string.
    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})`);
        }
      }
    }
  • src/config.ts:32-37 (registration)
    Specific configuration for the 'handbook-frames' tool, providing name, description, folder, and file used in the dynamic registration.
    {
      folder: 'handbook',
      file: '04_frames.md',
      name: 'handbook-frames',
      description: 'Turbo Frames for page decomposition - covers independent page segments, scoped navigation, eager/lazy loading, cache benefits, targeting navigation, frame promotion to visits, and custom rendering'
    },
  • Helper function to fetch markdown content from GitHub raw URL and cache it, used by readMarkdownFile for 'handbook/04_frames.md'.
    export async function fetchFromGitHub(filename: string, cacheKey?: string): Promise<string> {
      const githubUrl = `${GITHUB_RAW_BASE_URL}/${filename}`;
    
      console.error(`Fetching ${filename} from GitHub: ${githubUrl}`);
      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 full burden for behavioral disclosure. It describes technical aspects like 'cache benefits' and 'custom rendering' but does not specify whether this is a read-only, mutative, or informational tool, nor does it detail permissions, side effects, or response format. The gap is significant for a tool with no 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 run-on sentence listing multiple features without clear structure. While it avoids redundancy, it lacks front-loading of key purpose and could be more organized for readability, though it remains relatively concise.

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 no annotations, no output schema, and a vague description, the tool's functionality is inadequately explained. The description covers technical concepts but fails to clarify what the tool does, how it behaves, or what it returns, leaving significant gaps for agent understanding.

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 the schema fully documents the lack of inputs. The description does not add parameter information, which is unnecessary here. Baseline is 4 for zero parameters, as no compensation is needed.

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 lists technical features of 'Turbo Frames' but does not clearly state what the tool actually does. It mentions concepts like 'page decomposition', 'navigation', and 'loading' without specifying a verb or action the tool performs. While it distinguishes from siblings by focusing on frames, the purpose remains vague rather than explicit.

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?

No guidance is provided on when to use this tool versus alternatives. The description lists features but does not indicate context, prerequisites, or exclusions. Without explicit or implied usage scenarios, the agent lacks direction on application.

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

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