Skip to main content
Glama
ssql2014

Arcas OnlineEDA MCP Server

by ssql2014

arcas_onlineeda_project

Create, open, list, or delete electronic design automation projects for formal verification, equivalence checking, power analysis, security verification, and FPGA design on the Arcas OnlineEDA platform.

Instructions

Manage projects in OnlineEDA platform

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNo
projectNameNo
projectTypeNo
projectIdNo

Implementation Reference

  • The ProjectTool class that defines the tool name, description, schema, and execute logic for managing Arcas OnlineEDA projects (create, open, list, delete). Includes private helper methods for each action using browser automation.
    export class ProjectTool extends AbstractTool {
      constructor(browserManager: any) {
        super(ProjectSchema, browserManager);
      }
    
      getName(): string {
        return 'arcas_onlineeda_project';
      }
    
      getDescription(): string {
        return 'Manage projects in OnlineEDA platform';
      }
    
      protected async execute(params: ProjectParams): Promise<ToolResult> {
        await this.ensureLoggedIn();
        
        const page = this.browserManager.getPage();
        if (!page) {
          return {
            success: false,
            error: 'Browser page not available',
          };
        }
    
        try {
          switch (params.action) {
            case 'create':
              if (!params.projectName || !params.projectType) {
                return {
                  success: false,
                  error: 'Project name and type are required for creating a project',
                };
              }
              return await this.createProject(page, params.projectName, params.projectType);
            
            case 'open':
              if (!params.projectId) {
                return {
                  success: false,
                  error: 'Project ID is required for opening a project',
                };
              }
              return await this.openProject(page, params.projectId);
            
            case 'list':
              return await this.listProjects(page);
            
            case 'delete':
              if (!params.projectId) {
                return {
                  success: false,
                  error: 'Project ID is required for deleting a project',
                };
              }
              return await this.deleteProject(page, params.projectId);
            
            default:
              return {
                success: false,
                error: 'Unknown action',
              };
          }
        } catch (error) {
          return {
            success: false,
            error: `Project operation failed: ${error instanceof Error ? error.message : 'Unknown error'}`,
          };
        }
      }
    
      private async createProject(page: any, name: string, type: string): Promise<ToolResult> {
        // Navigate to new project page
        await page.goto('https://onlineeda.arcas-da.com/projects/new', { waitUntil: 'networkidle2' });
        
        // Fill in project details (selectors need to be adjusted based on actual UI)
        await page.waitForSelector('input[name="projectName"], #projectName');
        await page.type('input[name="projectName"], #projectName', name);
        
        // Select project type
        await page.select('select[name="projectType"], #projectType', type);
        
        // Submit form
        await Promise.all([
          page.click('button[type="submit"], .create-project-btn'),
          page.waitForNavigation({ waitUntil: 'networkidle2' }),
        ]);
        
        return {
          success: true,
          data: {
            projectName: name,
            projectType: type,
            message: 'Project created successfully',
          },
        };
      }
    
      private async openProject(page: any, projectId: string): Promise<ToolResult> {
        await page.goto(`https://onlineeda.arcas-da.com/projects/${projectId}`, { waitUntil: 'networkidle2' });
        
        return {
          success: true,
          data: {
            projectId,
            currentUrl: page.url(),
          },
        };
      }
    
      private async listProjects(page: any): Promise<ToolResult> {
        await page.goto('https://onlineeda.arcas-da.com/projects', { waitUntil: 'networkidle2' });
        
        // Extract project list (selectors need adjustment)
        const projects = await page.evaluate(() => {
          const projectElements = document.querySelectorAll('.project-item, .project-card');
          return Array.from(projectElements).map((el: any) => ({
            id: el.getAttribute('data-project-id') || el.id,
            name: el.querySelector('.project-name')?.textContent?.trim(),
            type: el.querySelector('.project-type')?.textContent?.trim(),
            status: el.querySelector('.project-status')?.textContent?.trim(),
          }));
        });
        
        return {
          success: true,
          data: {
            projects,
            count: projects.length,
          },
        };
      }
    
      private async deleteProject(page: any, projectId: string): Promise<ToolResult> {
        await page.goto(`https://onlineeda.arcas-da.com/projects/${projectId}/settings`, { waitUntil: 'networkidle2' });
        
        // Click delete button (with confirmation)
        await page.click('.delete-project-btn, button[data-action="delete"]');
        
        // Confirm deletion
        await page.waitForSelector('.confirm-delete, .modal-confirm');
        await page.click('.confirm-delete, button[data-confirm="delete"]');
        
        return {
          success: true,
          data: {
            projectId,
            message: 'Project deleted successfully',
          },
        };
      }
    }
  • Zod schema defining the input parameters for the arcas_onlineeda_project tool.
    const ProjectSchema = z.object({
      action: z.enum(['create', 'open', 'list', 'delete']).describe('Project action'),
      projectName: z.string().optional().describe('Project name'),
      projectType: z.enum(['formal', 'equivalence', 'power', 'security', 'fpga']).optional().describe('Project type'),
      projectId: z.string().optional().describe('Project ID for open/delete actions'),
    });
  • src/index.ts:52-64 (registration)
    Registration of the ProjectTool instance in the tools Map during server setup, using its getName() 'arcas_onlineeda_project' as the key.
    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);
      }
    }
Behavior1/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 but fails completely. 'Manage projects' doesn't indicate whether this is a read or write operation, what permissions are required, whether actions are destructive, what happens when projects are deleted, or what the response format looks like. For a tool with four actions including 'delete', this lack of behavioral information is critical.

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 extremely concise - a single five-word phrase. While this is efficient and front-loaded, it's so brief that it under-specifies rather than being appropriately sized. Every word earns its place, but there simply aren't enough words to be helpful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (four actions including potentially destructive operations), zero annotation coverage, zero schema description coverage, and no output schema, the description is completely inadequate. It doesn't explain what the tool does, how to use it, what parameters mean, what behaviors to expect, or what results will be returned. This leaves the agent with insufficient information to use the tool correctly.

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

Parameters1/5

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

The description provides zero information about any of the four parameters. With 0% schema description coverage (the schema only has basic type information without meaningful descriptions), the description fails to compensate by explaining what 'action', 'projectName', 'projectType', or 'projectId' mean, when they're required, or how they interact. The agent would have to guess parameter usage from the minimal schema alone.

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

Purpose2/5

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

The description 'Manage projects in OnlineEDA platform' is a tautology that essentially restates the tool name 'arcas_onlineeda_project'. It provides a generic verb ('manage') without specifying what management actions are available or what resources are involved. While it mentions 'projects', it doesn't distinguish this from sibling tools like 'arcas_onlineeda_navigate' or 'arcas_onlineeda_run_verification'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance about when to use this tool versus alternatives. It doesn't mention any of the four sibling tools, doesn't explain what types of project operations are available, and offers no context about prerequisites or appropriate use cases. The agent would have no idea when this tool is the right choice.

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