Skip to main content
Glama
lcapossio

fpgaZeroMCP

by lcapossio

place_and_route

Synthesize HDL code with Yosys and perform place-and-route with nextpnr for FPGA targets like ice40, ecp5, nexus, and gowin. Returns bitstream, timing, and resource usage.

Instructions

Synthesize HDL with Yosys then place-and-route with nextpnr in one step. Provide source as: code (single string), files (dict of filename→source), or project_dir (path to HDL files on disk). If backend=litex, runs LiteX build and ignores HDL inputs. Returns max frequency, critical path, resource utilization, bitstream, and full logs. Supported targets: ice40, ecp5, nexus, gowin. Common device/package values: ice40: device=hx1k|hx8k|up5k|lp1k package=tq144|qn84|sg48|cm81 ecp5: device=25k|45k|85k package=CABGA256|CABGA381 nexus: device=LIFCL-40-9BG400C (package embedded in device string) gowin: device=GW1N-UV4LQ144C6/I5 (package embedded in device string)

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_moduleYesTop-level module name
languageNoHDL language variantverilog
targetNoFPGA family
deviceNoDevice variant, e.g. 'hx1k', '25k', 'LIFCL-40-9BG400C'
packageNoPackage, e.g. 'tq144', 'CABGA256' (not needed for nexus/gowin)
constraintsNoOptional pin constraints (PCF/LPF/PDC/CST text)
timeoutNoPnR timeout in seconds
backendNoPnR backendyosys
litex_boardNoLiteX board target (required if backend=litex)
litex_argsNoExtra LiteX CLI args (backend=litex)
boardNoBoard preset (e.g. 'icebreaker', 'ulx3s_85f'). Sets target/device/package/clock automatically.
nextpnr_argsNoExtra nextpnr arguments (e.g. ['--seed', '42', '--placer', 'heap'])
work_dirNoPersistent working directory for incremental runs. Returned in response for reuse.
Behavior4/5

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

Given no annotations, the description discloses return values (max frequency, critical path, etc.), supported targets, and the behavior difference for litex backend. It lacks explicit statements on authorization or rate limits, but overall is fairly transparent.

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 front-loaded with the main purpose and then details mode specifics and device values. It is slightly lengthy but well-structured and informative.

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 the tool's complexity (16 parameters, multiple modes, nested objects, no output schema), the description covers all essential aspects: source modes, target families, return values, and special backend behavior.

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

Parameters5/5

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

Schema coverage is 100%, and the description adds valuable extra meaning, such as explaining the three source input modes and providing common device/package values, which goes beyond the schema 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 performs synthesis and place-and-route in one step, specifies multiple source input modes, and distinguishes from siblings like 'synthesize' and 'litex_build'.

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?

It provides clear context on when to use this combined step, including the special case for 'backend=litex'. However, it does not explicitly state when not to use it or mention alternatives beyond the sibling tool list.

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