Skip to main content
Glama

list_watched_files

Display all log files currently under active monitoring for real-time analysis and debugging purposes.

Instructions

List all currently monitored log files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'list_watched_files' that delegates to FileWatcher.listWatchedFiles() and formats the response as MCPToolResult.
    private async handleListWatchedFiles(args: any): Promise<MCPToolResult> {
      const watchedFiles = await this.fileWatcher.listWatchedFiles();
    
      return {
        success: true,
        data: watchedFiles
      };
    }
  • Input schema definition for the tool (empty object since no parameters required).
    inputSchema: {
      type: 'object',
      properties: {}
    }
  • src/server.ts:136-143 (registration)
    Tool registration in the ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: 'list_watched_files',
      description: 'List all currently monitored log files',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Helper method in FileWatcher class that lists all watched files with their status, recent errors count, and last update time.
    async listWatchedFiles(): Promise<FileWatchResult[]> {
      const results: FileWatchResult[] = [];
    
      for (const [filePath, watchedFile] of this.watchers) {
        results.push({
          filePath,
          newErrors: watchedFile.errors.slice(-5), // Last 5 errors
          totalErrors: watchedFile.errors.length,
          lastUpdate: watchedFile.lastUpdate
        });
      }
    
      return results;
    }
  • src/server.ts:189-191 (registration)
    Dispatch/registration case in the CallToolRequestSchema switch statement that routes to the handler.
    case 'list_watched_files':
      result = await this.handleListWatchedFiles(args);
      break;
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 states the action ('List') but doesn't describe what 'currently monitored' entails, whether this is a read-only operation, potential rate limits, or the format of the returned list. This leaves significant gaps for a tool that interacts with system resources.

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 that directly states the tool's purpose without any wasted words. It is front-loaded and appropriately sized for a simple tool with no parameters.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. However, it lacks details on behavioral aspects like what 'monitored' means or the return format, which could be important for an agent to use it correctly in context with sibling tools.

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 input schema has 0 parameters with 100% coverage, so no parameter information is needed. The description appropriately doesn't add parameter details, as there are none to document, aligning with the baseline for zero 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 verb ('List') and resource ('all currently monitored log files'), providing a specific purpose. However, it doesn't explicitly differentiate from sibling tools like 'get_recent_errors' or 'analyze_log', which might also involve log file operations but with different scopes or 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 such as 'get_recent_errors' or 'analyze_log'. It lacks context on prerequisites, timing, or exclusions, leaving the agent to infer usage from the tool name alone.

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/ChiragPatankar/loganalyzer-mcp'

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