Skip to main content
Glama
ssql2014

Arcas OnlineEDA MCP Server

by ssql2014

arcas_onlineeda_upload_file

Upload electronic design files to an OnlineEDA project for verification, analysis, and FPGA workflows using the Arcas platform.

Instructions

Upload design files to OnlineEDA project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNo
filePathNo
fileTypeNo

Implementation Reference

  • The protected async execute method implements the file upload logic: ensures login, navigates to project files page, uploads the local file via browser input, waits for success, returns result or error.
    protected async execute(params: UploadFileParams): Promise<ToolResult> {
      await this.ensureLoggedIn();
      
      const page = this.browserManager.getPage();
      if (!page) {
        return {
          success: false,
          error: 'Browser page not available',
        };
      }
    
      try {
        // Verify file exists
        const absolutePath = resolve(params.filePath);
        await fs.access(absolutePath);
        
        // Navigate to project files page
        await page.goto(`https://onlineeda.arcas-da.com/projects/${params.projectId}/files`, { 
          waitUntil: 'networkidle2' 
        });
        
        // Find file input element
        const fileInput = await page.$('input[type="file"]');
        if (!fileInput) {
          return {
            success: false,
            error: 'File upload input not found on page',
          };
        }
        
        // Upload file
        await fileInput.uploadFile(absolutePath);
        
        // Wait for upload to complete (adjust based on actual UI feedback)
        await page.waitForSelector('.upload-success, .file-uploaded', { timeout: 30000 });
        
        return {
          success: true,
          data: {
            projectId: params.projectId,
            fileName: absolutePath.split('/').pop(),
            filePath: params.filePath,
            message: 'File uploaded successfully',
          },
        };
      } catch (error) {
        return {
          success: false,
          error: `File upload failed: ${error instanceof Error ? error.message : 'Unknown error'}`,
        };
      }
    }
  • Zod schema defining input parameters: required projectId and filePath, optional fileType enum.
    const UploadFileSchema = z.object({
      projectId: z.string().describe('Project ID to upload file to'),
      filePath: z.string().describe('Local file path to upload'),
      fileType: z.enum(['verilog', 'systemverilog', 'vhdl', 'constraints', 'other']).optional().describe('File type'),
    });
  • src/index.ts:52-64 (registration)
    In setupTools method, UploadFileTool is instantiated with browserManager and added to the tools Map using its getName() as key for MCP tool registry.
    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);
      }
    }
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. While 'upload' implies a write operation, it doesn't specify permissions needed, file size limits, overwrite behavior, error conditions, or what happens after upload. This leaves significant gaps for a mutation tool.

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 communicates the core purpose without unnecessary words. It's appropriately sized for a basic upload operation and front-loads the essential information.

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 3-parameter mutation tool with no annotations, 0% schema coverage, and no output schema, the description is inadequate. It doesn't explain what happens after upload, error handling, or provide enough context about the parameters to use the tool effectively.

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%, meaning all 3 parameters are undocumented in the schema. The description mentions 'design files' and 'OnlineEDA project' which loosely map to 'filePath' and 'projectId', but provides no details about parameter formats, constraints, or the optional 'fileType' enum values. It doesn't adequately compensate for the schema gap.

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 ('upload') and target ('design files to OnlineEDA project'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'arcas_onlineeda_project' which might also handle project-related operations, keeping it from a perfect score.

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. With siblings like 'arcas_onlineeda_natural_language' and 'arcas_onlineeda_run_verification', there's no indication of when file upload is appropriate versus other project operations.

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