Skip to main content
Glama
lcapossio

fpgaZeroMCP

by lcapossio

synthesize

Synthesize HDL source code (Verilog, SystemVerilog, VHDL) using Yosys or LiteX backend. Returns resource statistics and inferred module list for FPGA targets like ice40, ecp5, and others.

Instructions

Synthesize HDL (Verilog, SystemVerilog, or VHDL) using Yosys or run LiteX backend. Provide source as: code (single string), files (dict of filename→source), or project_dir (path to HDL files on disk). Returns resource statistics and the list of inferred modules. Supported targets: generic, ice40, ecp5, gowin, xilinx, intel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoHDL source code (single-file mode)
filesNoMulti-file mode: mapping of filename to source code
project_dirNoDisk mode: path to directory containing HDL source files
top_moduleYesName of the top-level module
languageNoHDL language variantverilog
targetNoFPGA family / synthesis targetgeneric
backendNoSynthesis backendyosys
litex_boardNoLiteX board target (required if backend=litex)
litex_argsNoExtra LiteX CLI args (backend=litex)
timeoutNoTimeout in seconds
Behavior4/5

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

No annotations provided, so the description carries full burden. It discloses the synthesis process using Yosys/LiteX, output details, and source handling. No contradictions with annotations (none present).

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?

Three concise sentences front-load the main action, then explain source options, output, and targets. No redundant information; each sentence earns its place.

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

Completeness5/5

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

Given 10 parameters and no output schema, the description covers core functionality, input modes, supported targets, and return information. It is complete enough for an agent to understand and invoke the tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. The description adds value by summarizing the three source modes and output returns, providing a high-level understanding beyond individual parameter descriptions.

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

Purpose5/5

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

The description clearly states the tool synthesizes HDL using Yosys or LiteX backend, specifies source modes (code, files, project_dir), and mentions return type (resource statistics and module list). This distinguishes it from siblings like lint_hdl or simulate.

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

Usage Guidelines4/5

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

The description explains three source input modes and lists supported targets/backends, providing clear context for when to use this tool. It does not explicitly exclude alternatives or provide when-not-to-use, but the clarity of purpose suffices.

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/lcapossio/fpgaZeroMCP'

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