Skip to main content
Glama
lcapossio

fpgaZeroMCP

by lcapossio

lint_project

Lint multiple HDL files together to resolve cross-module references, supporting Verilog, SystemVerilog, and VHDL with optional -Wall checks via verilator.

Instructions

Lint multiple HDL files together so cross-module references resolve. Pass a dict of filename-to-source pairs. All files are compiled in one invocation of iverilog/verilator (Verilog/SystemVerilog) or ghdl (VHDL). Use linter='verilator' to enable -Wall checks including multidriven net detection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesYesMapping of filename to source code, e.g. {"uart_tx.v": "module uart_tx...", "top.v": "module top..."}
languageNoHDL language variantverilog
top_moduleNoTop-level module name (optional)
timeoutNoTimeout in seconds
linterNoLinter backend for Verilog/SV. 'verilator' enables -Wall (multidriven nets, etc.)iverilog
Behavior3/5

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

Discloses that all files are compiled in one invocation and mentions backend tools, but does not describe the output format (e.g., errors/warnings) or error handling. With no annotations, the description partially meets transparency needs.

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?

Two concise sentences, front-loaded with the core purpose, followed by specific technical detail. No redundant information.

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?

Covers multi-file and linter details, but lacks explanation of return values or behavior on lint errors. Given no output schema, the description should ideally mention what the agent can expect as output.

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% but the description adds extra value: explains the 'files' dictionary parameter with an example, elaborates on the 'linter' parameter (verilator -Wall), and implicitly ties 'language' to backend (ghdl for VHDL).

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 it lints multiple HDL files together with cross-module resolution, specifying the verb 'Lint' and the resource 'multiple HDL files'. It distinguishes from sibling 'lint_hdl' by focusing on multi-file compilation.

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?

Provides clear context for when to use (multi-file linting with cross-module resolution) and a specific recommendation for using 'verilator' to enable -Wall checks. However, it does not explicitly state when not to use or compare with sibling tools.

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