Skip to main content
Glama
ssql2014

Arcas OnlineEDA MCP Server

by ssql2014

arcas_onlineeda_navigate

Navigate to sections of the Arcas OnlineEDA platform including home, projects, documentation, and settings for electronic design automation workflows.

Instructions

Navigate to different sections of the OnlineEDA platform

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNo
projectIdNo

Implementation Reference

  • The main handler function that performs browser navigation to specific sections of the Arcas OnlineEDA platform based on the provided action parameter.
    protected async execute(params: NavigateParams): 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 'home':
            await page.goto('https://onlineeda.arcas-da.com/dashboard', { waitUntil: 'networkidle2' });
            break;
          
          case 'projects':
            await page.goto('https://onlineeda.arcas-da.com/projects', { waitUntil: 'networkidle2' });
            break;
          
          case 'new-project':
            await page.goto('https://onlineeda.arcas-da.com/projects/new', { waitUntil: 'networkidle2' });
            break;
          
          case 'documentation':
            await page.goto('https://onlineeda.arcas-da.com/docs', { waitUntil: 'networkidle2' });
            break;
          
          case 'settings':
            await page.goto('https://onlineeda.arcas-da.com/settings', { waitUntil: 'networkidle2' });
            break;
        }
    
        await page.waitForTimeout(1000); // Allow page to stabilize
    
        return {
          success: true,
          data: {
            action: params.action,
            currentUrl: page.url(),
          },
        };
      } catch (error) {
        return {
          success: false,
          error: `Navigation failed: ${error instanceof Error ? error.message : 'Unknown error'}`,
        };
      }
    }
  • Zod schema defining the input parameters for the navigate tool, including the required 'action' enum and optional 'projectId'.
    const NavigateSchema = z.object({
      action: z.enum(['home', 'projects', 'new-project', 'documentation', 'settings']).describe('Navigation action'),
      projectId: z.string().optional().describe('Project ID for project-specific navigation'),
    });
    
    type NavigateParams = z.infer<typeof NavigateSchema>;
  • src/index.ts:53-63 (registration)
    Registration of the NavigateTool instance in the tools map during server initialization, keyed by its getName() which returns 'arcas_onlineeda_navigate'.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description mentions 'navigate' but doesn't explain what this entails—e.g., whether it changes UI state, requires authentication, has side effects like loading pages, or handles errors. It lacks details on behavioral traits like rate limits, response format, or any platform-specific constraints, making it insufficient for a tool with no 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, clear sentence: 'Navigate to different sections of the OnlineEDA platform'. It's front-loaded with the core purpose, has zero waste, and is appropriately sized for a simple navigation tool. Every word earns its place by conveying the essential function without unnecessary elaboration.

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 the complexity (2 parameters, no annotations, no output schema), the description is incomplete. It doesn't address parameter usage, behavioral aspects like what 'navigate' returns or any side effects, or how it fits with sibling tools. For a tool with no structured data support, the description should provide more context to guide the agent effectively, but it falls short.

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 for undocumented parameters. The description doesn't mention any parameters, even though there are 2 (action and projectId). It fails to add meaning beyond the schema, such as explaining what 'action' values like 'home' or 'projects' do, or when 'projectId' is required. This leaves parameters largely unexplained, scoring low due to the coverage gap.

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's purpose as 'Navigate to different sections of the OnlineEDA platform', which is clear but vague. It specifies the verb 'navigate' and resource 'OnlineEDA platform', but doesn't distinguish from siblings like arcas_onlineeda_project or arcas_onlineeda_run_verification, which might also involve platform interactions. The purpose is understandable but lacks specificity about what 'navigate' entails compared to other tools.

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. It doesn't mention any context, prerequisites, or exclusions, such as when to choose this over sibling tools like arcas_onlineeda_natural_language for interactions. There's no explicit or implied usage advice, leaving the agent to infer based on 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/ssql2014/arcas-onlineeda-mcp'

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