Skip to main content
Glama
LexiconAlex

Better Auth MCP Server

by LexiconAlex

analyze_logs

Analyze authentication logs to identify security issues and anomalies within a specified time range for Better Auth MCP Server.

Instructions

Analyze Better-Auth logs for issues

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeRangeYesTime range to analyze (e.g. '24h', '7d')

Implementation Reference

  • Handler for the 'analyze_logs' tool. Extracts the timeRange argument, logs the analysis request, and returns a placeholder response indicating log analysis completion.
    case "analyze_logs": {
      const { timeRange } = request.params.arguments as { timeRange: string };
      logger.info(`Analyzing logs for time range: ${timeRange}`);
      // Implementation would analyze Better-Auth logs
      return {
        content: [{
          type: "text",
          text: `Log analysis complete for time range: ${timeRange}`
        }]
      };
    }
  • src/index.ts:169-182 (registration)
    Registration of the 'analyze_logs' tool in the listTools response, including name, description, and input schema.
    {
      name: "analyze_logs",
      description: "Analyze Better-Auth logs for issues",
      inputSchema: {
        type: "object",
        properties: {
          timeRange: {
            type: "string",
            description: "Time range to analyze (e.g. '24h', '7d')"
          }
        },
        required: ["timeRange"]
      }
    },
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 mentions analyzing logs for issues but does not specify whether this is a read-only operation, what permissions are required, how results are returned, or any rate limits. This is a significant gap for a tool that likely involves data processing without structured safety hints.

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, efficient sentence that directly states the tool's function. It is front-loaded and wastes no words, though it could benefit from more detail to improve utility. The brevity is appropriate but borders on under-specification given the lack of additional context.

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 the complexity of log analysis and the absence of annotations and output schema, the description is incomplete. It does not explain what 'analyze' entails, what issues it detects, or the format of results. With no structured fields to compensate, the description fails to provide sufficient context for effective tool use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the single parameter 'timeRange' documented as 'Time range to analyze (e.g., '24h', '7d')'. The description does not add any meaning beyond this, such as default values or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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's purpose as analyzing Better-Auth logs for issues, which is clear but vague. It specifies the resource (Better-Auth logs) and general action (analyze for issues), but lacks specificity on what 'analyze' entails or what types of issues it detects. It does not distinguish from siblings like 'analyze_current_auth' or 'monitor_auth_flows', which might have overlapping functions.

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. With siblings such as 'analyze_current_auth', 'monitor_auth_flows', and 'test_security', there is no indication of context, prerequisites, or exclusions. This leaves the agent without direction on selecting the appropriate tool for log analysis tasks.

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

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