Skip to main content
Glama
NellyW8

EDA Tools MCP Server

by NellyW8

view_waveform

Open VCD waveform files in GTKWave viewer to analyze simulation results for electronic design verification.

Instructions

Open VCD waveform file in GTKWave viewer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID from simulation (required)
vcd_fileNoVCD filename (default: output.vcd)output.vcd

Implementation Reference

  • Core handler implementation for the 'view_waveform' tool. Validates the project ID, locates the VCD file, checks for GTKWave availability, and launches GTKWave to display the waveform.
    async viewWaveform(projectId: string, vcdFile = "output.vcd"): Promise<string> {
      try {
        // Check if project exists
        const project = this.projects.get(projectId);
        if (!project) {
          return JSON.stringify({
            success: false,
            error: `Project ${projectId} not found. Run a simulation first.`,
          }, null, 2);
        }
    
        const vcdPath = join(project.dir, vcdFile);
    
        // Check if VCD file exists
        try {
          await fs.access(vcdPath);
        } catch {
          // List available files to help user
          const files = await fs.readdir(project.dir);
          const vcdFiles = files.filter(f => f.endsWith('.vcd'));
          
          return JSON.stringify({
            success: false,
            error: `VCD file '${vcdFile}' not found in project ${projectId}`,
            available_vcd_files: vcdFiles,
            note: "Make sure your testbench includes $dumpfile() and $dumpvars() commands"
          }, null, 2);
        }
    
        // Check if GTKWave is available
        if (!(await commandExists('gtkwave'))) {
          return JSON.stringify({
            success: false,
            error: "GTKWave not found. Please install GTKWave to view waveforms.",
            install_instructions: {
              macos: "brew install gtkwave",
              linux: "sudo apt-get install gtkwave",
              windows: "Install GTKWave from http://gtkwave.sourceforge.net/"
            }
          }, null, 2);
        }
    
        // Launch GTKWave in background
        const gtkwaveCmd = `gtkwave "${vcdPath}" &`;
        await execAsync(gtkwaveCmd, { 
          cwd: project.dir, 
          timeout: 5000 
        });
    
        return JSON.stringify({
          success: true,
          message: `GTKWave launched for project ${projectId}`,
          vcd_file: vcdFile,
          vcd_path: vcdPath,
          project_type: project.type
        }, null, 2);
    
      } catch (error: any) {
        return JSON.stringify({
          success: false,
          error: error.message || String(error),
        }, null, 2);
      }
    }
  • src/index.ts:768-785 (registration)
    Registration of the 'view_waveform' tool in the MCP server's tool list, including description and input schema definition.
      name: "view_waveform",
      description: "Open VCD waveform file in GTKWave viewer",
      inputSchema: {
        type: "object",
        properties: {
          project_id: { 
            type: "string", 
            description: "Project ID from simulation (required)" 
          },
          vcd_file: { 
            type: "string", 
            description: "VCD filename (default: output.vcd)",
            default: "output.vcd"
          },
        },
        required: ["project_id"],
      },
    },
  • Tool dispatch handler in the CallToolRequestSchema that extracts parameters and invokes the EDAServer.viewWaveform method.
    case "view_waveform": {
      const projectId = validateRequiredString(args, "project_id", name);
      const vcdFile = getStringProperty(args, "vcd_file", "output.vcd");
      
      return {
        content: [{
          type: "text",
          text: await edaServer.viewWaveform(projectId, vcdFile),
        }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention whether this opens a GUI, requires specific permissions, affects system state, or has side effects like launching external applications, which is inadequate for a tool with zero annotation coverage.

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 front-loads the core purpose without any wasted words. It directly conveys the tool's function in a structured and concise manner.

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 no annotations, no output schema, and a tool that likely involves external application interaction (GTKWave), the description is incomplete. It doesn't explain what happens after opening (e.g., viewer launch, error handling), return values, or prerequisites, leaving significant gaps for an agent to use it 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 description adds no parameter semantics beyond what the input schema provides, which has 100% coverage with clear descriptions for both parameters. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Open'), the resource type ('VCD waveform file'), and the target application ('GTKWave viewer'), which distinguishes it from sibling tools like view_gds (for GDS files) or simulate_verilog (for simulation).

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 view_gds (for viewing layout) or simulate_verilog (which might generate waveforms). It lacks explicit when/when-not instructions or named alternatives, leaving usage context implied at best.

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/NellyW8/MCP4EDA'

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