Skip to main content
Glama
ssql2014

Arcas OnlineEDA MCP Server

by ssql2014

arcas_onlineeda_natural_language

Process natural language queries to perform electronic design automation operations like formal verification, equivalence checking, and FPGA design analysis.

Instructions

Process natural language queries for Arcas OnlineEDA operations with extensive examples

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
contextNo

Implementation Reference

  • The core handler function that processes natural language input, matches against examples, detects intent, and returns suggested tools and parameters.
    protected async execute(params: NaturalLanguageParams): Promise<ToolResult> {
      const query = params.query.toLowerCase();
      
      try {
        // First check for exact or close matches in examples
        const exactMatch = this.findBestExample(query);
        if (exactMatch) {
          return {
            success: true,
            data: {
              interpretation: exactMatch.interpretation,
              suggestedTool: exactMatch.tool,
              suggestedParams: exactMatch.params,
              matchedExample: exactMatch.query,
              confidence: 'high',
            },
          };
        }
    
        // Parse intent from natural language with enhanced understanding
        if (this.isProjectCreation(query)) {
          return this.suggestProjectCreation(query);
        }
        
        if (this.isVerification(query)) {
          return this.suggestVerification(query);
        }
        
        if (this.isFileOperation(query)) {
          return this.suggestFileUpload(query);
        }
        
        if (this.isNavigation(query)) {
          return this.suggestNavigation(query);
        }
        
        if (this.isResultsQuery(query)) {
          return this.suggestGetResults(params.context?.currentProject);
        }
        
        if (this.isHelpQuery(query)) {
          return this.provideEnhancedHelp();
        }
        
        // Fallback with examples
        return this.provideFallbackWithExamples(params.query);
      } catch (error) {
        return {
          success: false,
          error: `Natural language processing failed: ${error instanceof Error ? error.message : 'Unknown error'}`,
        };
      }
    }
  • Zod schema defining the input parameters for the natural language tool.
    const NaturalLanguageSchema = z.object({
      query: z.string().describe('Natural language query about Arcas OnlineEDA operations'),
      context: z.object({
        currentProject: z.string().optional().describe('Current project ID'),
        previousResults: z.any().optional().describe('Previous operation results'),
      }).optional(),
    });
  • src/index.ts:52-64 (registration)
    Registration of the NaturalLanguageTool instance in the MCP server's tools map, along with other tools.
    private setupTools(): void {
      const toolInstances = [
        new NavigateTool(this.browserManager),
        new ProjectTool(this.browserManager),
        new UploadFileTool(this.browserManager),
        new RunVerificationTool(this.browserManager),
        new NaturalLanguageTool(this.browserManager),
      ];
    
      for (const tool of toolInstances) {
        this.tools.set(tool.getName(), tool);
      }
    }
  • Extensive list of example queries and their corresponding tool mappings used for intent matching and suggestion.
    private examples: Example[] = [
      // Project creation examples
      {
        query: "I want to create a new formal verification project for my CPU design",
        interpretation: "Create formal verification project",
        tool: "arcas_onlineeda_project",
        params: { action: "create", projectType: "formal", projectName: "cpu_formal_verification" }
      },
      {
        query: "Let's start a power analysis project for the GPU controller",
        interpretation: "Create power analysis project",
        tool: "arcas_onlineeda_project",
        params: { action: "create", projectType: "power", projectName: "gpu_controller_power" }
      },
      {
        query: "Set up equivalence checking between RTL and gate-level netlist",
        interpretation: "Create equivalence checking project",
        tool: "arcas_onlineeda_project",
        params: { action: "create", projectType: "equivalence", projectName: "rtl_gate_equivalence" }
      },
      
      // Verification examples
      {
        query: "Check if my RISC-V core meets all safety properties",
        interpretation: "Run formal verification with safety properties",
        tool: "arcas_onlineeda_run_verification",
        params: { verificationType: "formal", options: { properties: ["safety"], depth: 20 } }
      },
      {
        query: "Verify that the optimized design is functionally equivalent to the original",
        interpretation: "Run equivalence verification",
        tool: "arcas_onlineeda_run_verification",
        params: { verificationType: "equivalence" }
      },
      {
        query: "Analyze power consumption during different operating modes",
        interpretation: "Run power analysis verification",
        tool: "arcas_onlineeda_run_verification",
        params: { verificationType: "power", options: { timeout: 600 } }
      },
      {
        query: "Find security vulnerabilities in my crypto module",
        interpretation: "Run security verification",
        tool: "arcas_onlineeda_run_verification",
        params: { verificationType: "security", options: { properties: ["information_leakage", "timing_attacks"] } }
      },
      
      // File operations examples
      {
        query: "Upload my Verilog files for the memory controller",
        interpretation: "Upload Verilog design files",
        tool: "arcas_onlineeda_upload_file",
        params: { fileType: "verilog" }
      },
      {
        query: "Add the SystemVerilog testbench to the project",
        interpretation: "Upload SystemVerilog testbench",
        tool: "arcas_onlineeda_upload_file",
        params: { fileType: "systemverilog" }
      },
      {
        query: "Import SDC timing constraints",
        interpretation: "Upload constraint files",
        tool: "arcas_onlineeda_upload_file",
        params: { fileType: "constraints" }
      },
      
      // Navigation examples
      {
        query: "Show me all my verification projects",
        interpretation: "Navigate to projects list",
        tool: "arcas_onlineeda_navigate",
        params: { action: "projects" }
      },
      {
        query: "Go to the documentation",
        interpretation: "Navigate to documentation",
        tool: "arcas_onlineeda_navigate",
        params: { action: "documentation" }
      },
      
      // Complex workflow examples
      {
        query: "I need to verify my AES encryption module meets FIPS standards",
        interpretation: "Security verification workflow for cryptographic module",
        tool: "workflow",
        params: {
          steps: [
            { tool: "arcas_onlineeda_project", params: { action: "create", projectType: "security", projectName: "aes_fips_verification" } },
            { tool: "arcas_onlineeda_upload_file", params: { fileType: "verilog" } },
            { tool: "arcas_onlineeda_run_verification", params: { verificationType: "security", options: { properties: ["fips_compliance"] } } }
          ]
        }
      },
      {
        query: "Compare power consumption before and after optimization",
        interpretation: "Power comparison workflow",
        tool: "workflow", 
        params: {
          steps: [
            { tool: "arcas_onlineeda_project", params: { action: "create", projectType: "power", projectName: "optimization_comparison" } },
            { tool: "arcas_onlineeda_upload_file", params: { fileType: "verilog", note: "Upload both versions" } },
            { tool: "arcas_onlineeda_run_verification", params: { verificationType: "power" } }
          ]
        }
      }
    ];
  • src/index.ts:20-20 (registration)
    Import statement for the NaturalLanguageTool class.
    import { NaturalLanguageTool } from './tools/natural-language.js';
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'process' and 'extensive examples' but doesn't disclose behavioral traits like whether this is a read-only or mutating operation, authentication needs, rate limits, error handling, or what 'process' entails (e.g., returns results, executes commands). This leaves significant gaps for a tool with 2 parameters and no output schema.

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's appropriately sized. It's front-loaded with the core purpose ('Process natural language queries...'), though the 'extensive examples' part feels tacked on without clear value. There's minimal waste, but it could be more structured with clearer separation of purpose and usage.

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 2 parameters with 0% schema coverage, no annotations, no output schema, and sibling tools, the description is incomplete. It doesn't explain what the tool returns, how it differs from other tools, or provide enough context for safe and effective use. For a natural language processing tool in a technical domain like EDA, more detail on behavior and outputs is needed.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions 'natural language queries' which aligns with the 'query' parameter, but doesn't explain the 'context' parameter at all. The phrase 'extensive examples' might hint at usage but adds no specific semantics about parameter formats, constraints, or relationships. This fails to adequately cover the 2 undocumented parameters.

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 'Process natural language queries for Arcas OnlineEDA operations' which provides a clear verb ('process') and resource ('natural language queries'), but it doesn't specify what type of processing occurs (e.g., interpretation, translation, execution) or how it differs from sibling tools like 'arcas_onlineeda_navigate' or 'arcas_onlineeda_project'. The mention of 'extensive examples' is vague about purpose.

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 explicit guidance on when to use this tool versus alternatives. It mentions 'extensive examples' which might imply usage for complex queries, but there's no clear when/when-not criteria or named alternatives. Without context, it's unclear if this is for general queries, specific operations, or how it complements other tools.

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/ssql2014/arcas-onlineeda-mcp'

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