Skip to main content
Glama
Sign In
Vivado MCP

Vivado MCP

by binghin2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

run_synthesis

Run synthesis on the current Vivado project with configurable parallel jobs and timeout, so you can generate a synthesized netlist before implementation.

Instructions

Run synthesis on the current project

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_synthesis"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobsNoNumber of parallel jobs (default: 4)
timeoutNoTimeout in seconds (default: 1800 = 30 minutes). Increase for large designs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior1/5

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

With no annotations, the description carries full burden for behavioral disclosure. It provides no information about side effects, typical runtime, failure conditions, or safety profile. The agent cannot infer whether this is a safe read, destructive write, or long-running process.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at one sentence. However, it may be too brief, sacrificing necessary completeness. While it earns its place by stating the core action, it does not provide enough value for a tool with 2 parameters and no output schema.

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?

The tool has no output schema and minimal description. Critical context is missing: whether synthesis produces output files, how to check results, what errors can occur, or that it may take significant time. The description is insufficient for an agent to use this tool reliably.

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?

Although the description adds no parameter information, the input schema already fully describes both parameters (jobs and timeout) with defaults and usage hints. Parameter schema coverage is 100%, so the baseline 3 is appropriate.

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 'Run synthesis on the current project' is essentially a tautology of the tool name. It adds minimal context (the implicit 'current project'), but fails to specify what synthesis accomplishes or how it differs from sibling tools like 'run_implementation'.

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?

No usage guidelines are provided. The description does not indicate when to use this tool (e.g., after opening a project, before implementation), nor does it mention any prerequisites or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools