Skip to main content
Glama
pinzonjulian

Turbo Docs MCP Server

by pinzonjulian

reference-attributes

Access comprehensive documentation for Turbo data attributes and meta tags to control Drive behavior, frame navigation, and caching functionality.

Instructions

Complete reference for Turbo data attributes and meta tags - covers all data-turbo-* attributes for controlling Drive behavior, frame navigation, caching, and automatically added attributes like aria-busy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the tool logic for 'reference-attributes': reads the markdown content from 'reference/attributes.md' via readMarkdownFile and returns it as a text content block in MCP format, 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)
    Registers the 'reference-attributes' tool (along with other doc tools) on the MCP server using server.tool(), with name and description from config, and the shared 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}`
                }
              ]
            };
          }
        }
      );
    });
  • Configuration entry in docFiles array that defines the tool name 'reference-attributes', its corresponding doc file path 'reference/attributes.md', and description used in registration.
      folder: 'reference',
      file: 'attributes.md',
      name: 'reference-attributes',
      description: 'Complete reference for Turbo data attributes and meta tags - covers all data-turbo-* attributes for controlling Drive behavior, frame navigation, caching, and automatically added attributes like aria-busy'
    },
  • Supporting function called by the handler to fetch markdown content for 'reference/attributes.md' from cache, GitHub raw file, or local filesystem, with commit-based caching.
    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 of behavioral disclosure. It describes the content ('complete reference') but does not specify behavioral traits such as whether it returns static data, requires authentication, has rate limits, or involves any side effects. For a tool with zero annotation coverage, this is a significant gap in transparency, though it avoids contradiction.

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 tool's purpose and scope. It is front-loaded with key information ('complete reference for Turbo data attributes and meta tags') and adds specific details without redundancy. However, it could be slightly more concise by avoiding the dash and integrating the list more smoothly, but overall it is highly efficient.

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's complexity (a reference tool with no parameters) and the absence of annotations and output schema, the description is adequate but not complete. It covers what the tool provides but lacks details on behavioral aspects, return format, or how it integrates with sibling tools. For a reference tool, more context on usage and output would enhance completeness, but it meets minimum viability.

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, and schema description coverage is 100%, so no parameter information is needed. The description appropriately does not discuss parameters, focusing instead on the tool's purpose and scope. This meets the baseline for tools with no parameters, as it avoids unnecessary details and compensates well for the lack of parameters.

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: to provide a 'complete reference for Turbo data attributes and meta tags.' It specifies the scope ('all data-turbo-* attributes') and key areas covered ('controlling Drive behavior, frame navigation, caching, and automatically added attributes like aria-busy'). However, it does not explicitly differentiate from sibling tools like 'reference-drive' or 'reference-frames,' which might overlap in topic, preventing a score of 5.

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 offers no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or specific contexts for usage. While it implies a reference or documentation purpose, it lacks explicit instructions on when this tool is appropriate compared to sibling tools like 'handbook-building' or other reference tools, 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/turbo-docs-mcp-server'

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