Skip to main content
Glama
pinzonjulian

Turbo Docs MCP Server

by pinzonjulian

handbook-drive

Access Turbo Drive documentation to implement fast page navigation, covering page visits, form submissions, caching, prefetching, and view transitions.

Instructions

Turbo Drive navigation guide - covers page visits, application/restoration visits, link handling, form submissions, progress indicators, caching, prefetching, and view transitions for fast page navigation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function executed when the 'handbook-drive' tool is called. It reads the content of the associated markdown file ('handbook/02_drive.md') using readMarkdownFile and returns it as a text 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}`
            }
          ]
        };
      }
    }
  • src/index.ts:17-45 (registration)
    Registration of the 'handbook-drive' tool (and other doc tools) by iterating over the docFiles config and calling server.tool(name, description, handler) for each.
    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}`
                }
              ]
            };
          }
        }
      );
    });
  • Configuration defining the metadata (name, description) and content source (folder/file) for the 'handbook-drive' tool.
    folder: 'handbook',
    file: '02_drive.md',
    name: 'handbook-drive',
    description: 'Turbo Drive navigation guide - covers page visits, application/restoration visits, link handling, form submissions, progress indicators, caching, prefetching, and view transitions for fast page navigation'
  • Core helper function readMarkdownFile that implements the logic to fetch markdown content from cache, GitHub raw, or local fallback, called by the tool handler.
    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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool as a 'guide' covering topics, implying it's informational and likely read-only, but doesn't explicitly state whether it's a reference document, tutorial, or interactive tool. It lacks details on output format, access requirements, or any operational constraints like rate limits or side effects.

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 topics without clear structure or prioritization. While it efficiently covers many aspects of Turbo Drive navigation, it could be more front-loaded with a concise purpose statement (e.g., 'Guide to Turbo Drive navigation features') followed by key topics. The list-like format is somewhat cluttered but not excessively verbose.

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 adequate context about what the guide covers. However, for a handbook/guide tool among many siblings, it could better clarify its unique value versus similar tools (e.g., 'handbook-frames') and expected output format. The description is minimally viable but leaves gaps in usage context.

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 doesn't discuss parameters, focusing instead on the tool's content scope. This meets the baseline for tools with no parameters, as there's nothing to compensate for in terms of schema coverage.

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 as a 'navigation guide' covering specific Turbo Drive features like page visits, link handling, form submissions, and caching. It distinguishes itself from siblings by focusing on 'navigation' aspects rather than installation, building, or reference topics, though it doesn't explicitly contrast with similar tools like 'handbook-frames' or 'reference-drive'.

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 covered topics but doesn't indicate scenarios where this guide is preferred over sibling tools like 'handbook-frames' for frame-related navigation or 'reference-drive' for technical reference. There's no mention of prerequisites, target audience, or use-case exclusions.

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