Skip to main content
Glama
dabhivijay2478

Better Auth MCP Server

get_llms_context

Retrieve Better Auth LLMs.txt content to access comprehensive authentication framework documentation and configuration details for development.

Instructions

Get Better Auth LLMs.txt content for comprehensive context

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of the 'get_llms_context' tool. It fetches the LLMs.txt file from Better Auth documentation site using axios and returns the content wrapped in a standardized response format.
    private async handleGetLlmsContext() {
      try {
        const response = await this.axiosInstance.get(`${this.BETTER_AUTH_DOCS_URL}/llms.txt`);
        
        return this.createSuccessResponse({
          source: "https://www.better-auth.com/llms.txt",
          content: response.data,
          lastUpdated: new Date().toISOString(),
        });
      } catch (error) {
        this.handleAxiosError(error, "Failed to fetch Better Auth LLMs context");
      }
    }
  • src/index.ts:209-217 (registration)
    Registration of the 'get_llms_context' tool in the list of available tools, including its name, description, and input schema (which is empty as the tool takes no parameters).
    {
      name: "get_llms_context",
      description: "Get Better Auth LLMs.txt content for comprehensive context",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • src/index.ts:233-234 (registration)
    Dispatch case in the CallToolRequestSchema handler that routes calls to the 'get_llms_context' tool to its handler function.
    case "get_llms_context":
      return await this.handleGetLlmsContext();
  • The input schema for the tool, defining it as an empty object with no required properties.
    inputSchema: {
      type: "object",
      properties: {},
      required: [],
    },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool 'gets' content, implying a read operation, but doesn't disclose any behavioral traits like whether it requires authentication, has rate limits, returns structured vs unstructured data, or what happens if the file doesn't exist.

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 sentence that efficiently states the core purpose. While it could be more specific about what 'comprehensive context' entails, there's no wasted verbiage or unnecessary repetition.

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?

For a tool with no annotations, no output schema, and zero parameters, the description is insufficient. It doesn't explain what format the content returns (text, JSON, etc.), whether it's the entire file or a summary, or how this differs from sibling tools that might provide similar information.

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 with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description appropriately doesn't add parameter information beyond what the schema provides, maintaining the baseline score for this situation.

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 states the tool retrieves content from 'Better Auth LLMs.txt', which provides a specific resource. However, it's vague about what 'comprehensive context' means and doesn't differentiate from sibling tools like 'get_auth_examples' or 'search_better_auth' that might also provide contextual information.

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 doesn't mention any prerequisites, timing considerations, or comparisons to sibling tools like 'get_auth_examples' or 'search_better_auth' that might serve similar purposes.

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/dabhivijay2478/better-auth-mcp-server'

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