gowin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gowin_list_buildsA | Find Gowin EDA builds under a directory tree. Returns project name, device, and when each was built, newest first. |
| gowin_summaryA | Headline report for one build: device, resource usage, fMax per clock, and every timing violation. Start here. |
| gowin_resourcesA | Full resource usage for one build: logic, CLS, registers, BSRAM, DSP, I/O banks and clock resources. |
| gowin_timingA | Timing detail for one build: fMax per clock, total negative slack, and the worst setup/hold paths with their endpoints. |
| gowin_checkA | Pass/fail gate. Returns only the timing violations, with the offending path for each. Empty means the build closed timing. |
| gowin_compareA | Diff two builds: resource deltas, fMax change per clock, and which violations were introduced, fixed, or persist. Use this to see what a change actually cost. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of Gowin EDA builds: listing, summary, resources, timing, pass/fail check, and comparison. No overlap in purposes.
All tools follow the consistent pattern 'gowin_<action>', using snake_case throughout.
Six tools cover the full workflow of build analysis without being excessive or insufficient.
Covers all major aspects (listing, resources, timing, check, comparison). Minor gap: no tool for raw build metadata or logs, but summary compensates.