Skip to main content
Glama
mariosss

Local Logs MCP Server

by mariosss

watch_log

Monitor a log file for real-time changes to track errors and debug applications by tailing log entries as they occur.

Instructions

Monitor a log file for changes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameNoName of the log file to monitor (default: combined.log)combined.log

Implementation Reference

  • The watchLog method implements the core logic for the 'watch_log' tool. It checks if the specified log file exists, retrieves file stats, and returns monitoring status information.
    watchLog(filename = 'combined.log') {
      try {
        const filePath = path.join(this.logsDir, filename);
        
        if (!fs.existsSync(filePath)) {
          return { 
            watching: false, 
            message: `Log file ${filename} not found`,
            filename 
          };
        }
    
        const stats = fs.statSync(filePath);
        return { 
          watching: true, 
          file: filename,
          size: stats.size,
          sizeHuman: this.formatBytes(stats.size),
          lastModified: stats.mtime.toISOString(),
          message: `Monitoring ${filename} for changes`
        };
      } catch (error) {
        return { watching: false, error: error.message, filename };
      }
    }
  • Input schema for the 'watch_log' tool, defining the optional 'filename' parameter with default value.
    inputSchema: {
      type: 'object',
      properties: {
        filename: {
          type: 'string',
          description: 'Name of the log file to monitor (default: combined.log)',
          default: 'combined.log'
        }
      },
      required: []
    }
  • Tool registration in the 'tools/list' response, including name, description, and schema.
    {
      name: 'watch_log',
      description: 'Monitor a log file for changes',
      inputSchema: {
        type: 'object',
        properties: {
          filename: {
            type: 'string',
            description: 'Name of the log file to monitor (default: combined.log)',
            default: 'combined.log'
          }
        },
        required: []
      }
    },
  • Dispatch case in handleToolCall that routes 'watch_log' calls to the watchLog method.
    case 'watch_log':
      result = this.watchLog(args?.filename);
      break;
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. 'Monitor a log file for changes' implies an ongoing or real-time operation but doesn't specify whether this is a blocking call, how changes are detected, what format output takes, or any rate limits. The description is too vague about actual behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the core functionality immediately.

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 monitoring tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'monitor' means operationally, what constitutes 'changes', how results are returned, or how this differs from similar sibling tools. The agent would struggle to use this effectively.

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 'filename' well-documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema, so the baseline score of 3 is appropriate.

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 action ('monitor') and resource ('log file for changes'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'tail_log' or 'search_logs', which likely have overlapping functionality with log monitoring.

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 like 'tail_log' or 'search_logs'. It doesn't specify whether this is for real-time monitoring, periodic checking, or other specific contexts, leaving the agent with no usage differentiation.

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/mariosss/local-logs-mcp-server'

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