Skip to main content
Glama
pinzonjulian

Turbo Docs MCP Server

by pinzonjulian

handbook-native

Access documentation for developing mobile apps using Turbo-enabled web views with native navigation for iOS and Android hybrid applications.

Instructions

Hotwire Native for mobile apps - overview of iOS and Android native app development using Turbo-enabled web views for hybrid applications with native navigation and web content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Anonymous async handler function for the 'handbook-native' tool, which reads the markdown content from 'handbook/06_native.md' via readMarkdownFile and returns it as an MCP text content block, with error handling.
    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)
    Dynamic registration of the 'handbook-native' tool by iterating over the docFiles configuration 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}`
                }
              ]
            };
          }
        }
      );
    });
  • src/config.ts:44-49 (registration)
    Configuration object in the docFiles array defining the metadata (name, description, source file) used to register the 'handbook-native' tool.
    {
      folder: 'handbook',
      file: '06_native.md',
      name: 'handbook-native',
      description: 'Hotwire Native for mobile apps - overview of iOS and Android native app development using Turbo-enabled web views for hybrid applications with native navigation and web content'
    },
  • Helper function readMarkdownFile used by the tool handler to retrieve the content of the specified documentation file, supporting caching, GitHub API fetches, and 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the content topic but doesn't mention whether this is a read-only reference, if it requires authentication, how data is presented (e.g., text, examples), or any limitations like scope or depth. This leaves significant gaps for an agent to understand how to interact with the tool.

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, well-structured sentence that efficiently conveys the core topic. It's front-loaded with key terms like 'Hotwire Native,' 'mobile apps,' and 'overview,' avoiding redundancy. However, it could be slightly more concise by removing minor wordiness (e.g., 'for hybrid applications' might be implied).

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 output schema, and no annotations, the description provides a basic overview but lacks depth. It doesn't explain what the tool returns (e.g., documentation text, links, examples) or how it fits into the broader context of sibling tools. For a reference tool, this is minimally adequate but leaves room for improvement in guiding usage.

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 zero parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to compensate for any gaps, earning a baseline score of 4 for adequately addressing the parameter-less nature without unnecessary detail.

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: providing an overview of iOS and Android native app development using Turbo-enabled web views for hybrid applications. It specifies the resource (mobile app development) and approach (Turbo-enabled web views with native navigation and web content), though it doesn't explicitly differentiate from sibling tools like 'handbook-building' or 'handbook-introduction'.

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 explicit guidance is provided on when to use this tool versus alternatives. The description implies it's for learning about hybrid app development with Turbo, but it doesn't specify prerequisites, target audience, or how it complements other handbook tools like 'handbook-installing' or 'handbook-frames'.

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