Skip to main content
Glama

Create or update Quartus project

quartus_create_project

Create a Quartus project or revision by specifying device, top-level entity, source files, pin assignments, and board presets. Automates project setup using Tcl commands.

Instructions

Create a Quartus project/revision with device, top entity, HDL/SDC files, pin assignments, and generic assignments using Quartus Tcl.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
installRootNoQuartus root. Accepts either the Quartus install directory or its parent.
use64bitNoUse quartus/bin64 when available. Defaults to true.
projectDirYesDirectory to create/open the project in.
projectNameYesQuartus project name without .qpf.
revisionNoRevision name. Defaults to projectName.
overwriteNoOverwrite an existing project/revision. Defaults to false.
boardPresetNoBoard preset id. Use quartus_list_board_presets to inspect available presets.
applyBoardDefaultsNoApply board preset family/device/common assignments. Defaults to true when boardPreset is provided.
familyNoFPGA family, for example Cyclone.
deviceNoExact device, for example EP1C6F256C6.
topLevelEntityNoTop-level entity/module name.
sourceFilesNoHDL, BDF, QIP, SDC, VWF, or other project files.
sdcFilesNoTiming constraint files. Added as SDC_FILE.
globalAssignmentsNoAdditional set_global_assignment items.
locationAssignmentsNoPin/location assignments such as {to:'clk', location:'PIN_G1'}.
resourceBindingsNoPin assignments derived from a board preset resource library.
instanceAssignmentsNoAdditional set_instance_assignment items.
timeoutSecondsNo
Behavior2/5

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

No annotations are provided, so the description should disclose behavioral traits. It mentions 'using Quartus Tcl' and the overwrite parameter, but does not reveal whether the tool is destructive, authentication requirements, side effects (e.g., file system changes), or limits on concurrent operations.

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 sentence that is concise, front-loaded with the core purpose, and contains no extraneous information. Every word contributes to understanding the tool's function.

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

Completeness3/5

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

Given the tool's complexity (18 parameters, 2 required), the description covers the main functional areas but omits some parameter groups like resourceBindings, instanceAssignments, and timeout. The rich schema compensates partially, but the description alone is not fully comprehensive.

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?

Schema description coverage is 94%, so most parameters are already documented. The description lists high-level categories (HDL/SDC files, pin assignments) but does not add significant meaning beyond the schema. For example, 'resourceBindings' is not mentioned in the description.

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 specifies 'Create a Quartus project/revision' with a clear verb and resource, and lists the key elements (device, top entity, files, assignments). It distinguishes the tool from siblings like quartus_list_projects (listing) and quartus_run_flow (execution).

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

Usage Guidelines3/5

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

The description implies usage for project creation/update but does not provide explicit guidance on when to use this tool versus alternatives like quartus_run_tcl or quartus_set_pins. No when-not-to-use criteria or prerequisites are mentioned.

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/alglb123/quartus91-mcp'

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