Skip to main content
Glama
Papipapito

gowin-mcp

by Papipapito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Timing detail

gowin_timing
Read-onlyIdempotent

Parse Gowin EDA build reports to extract fMax per clock, worst setup/hold paths, and recovery/removal summaries.

Instructions

Timing detail for one build: fMax per clock, total negative slack, the worst setup/hold paths with their endpoints, and a summary of the recovery/removal checks. The path tables are trimmed to the worst maxPaths entries in both renderings; paths="all" returns every parsed path, paths="none" only the summaries plus worstSetup/worstHold.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoWhen several builds share one impl/pnr/, pick this one by name (the <name> of <name>.rpt.txt). Default: the most recent, with the others listed under siblings.
pathYesPath to the build: the project directory, its impl/ directory, impl/pnr/ itself, or the .rpt.txt. Either kind of slash.
pathsNoworst (default): the maxPaths worst of each table; all: every parsed path; none: no path tables.
formatNoOutput format. Default text: a compact rendering, returned as the only content. json: the full JSON as text and as structuredContent.
maxPathsNoWorst paths to keep per table (text and JSON), default 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / format / description
      Previous value: -"Output format. Defaults to text, which is far more compact."New value: +"Output format. Default text: a compact rendering, returned as the only content. json: the full JSON as text and as structuredContent."
    • changedInput schema / properties / maxPaths / description
      Previous value: -"Worst paths to show, default 10."New value: +"Worst paths to keep per table (text and JSON), default 10."
    • addedInput schema / properties / name
      Added value: +{
+  "description": "When several builds share one impl/pnr/, pick this one by name (the <name> of <name>.rpt.txt). Default: the most recent, with the others listed under siblings.",
+  "type": "string"
+}
    • changedInput schema / properties / path / description
      Previous value: -"Path to the build: the project directory, its impl/ directory, or the .rpt.txt itself."New value: +"Path to the build: the project directory, its impl/ directory, impl/pnr/ itself, or the .rpt.txt. Either kind of slash."
    • addedInput schema / properties / paths
      Added value: +{
+  "description": "worst (default): the maxPaths worst of each table; all: every parsed path; none: no path tables.",
+  "enum": [
+    "worst",
+    "all",
+    "none"
+  ],
+  "type": "string"
+}
  2. First observedv0.1.0-beta.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real value beyond that by disclosing the returned content, the maxPaths trimming behavior, and the distinction between text and JSON renderings.

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 sentences, front-loaded with the returned content, then the trimming and paths-mode behavior. No filler; every clause 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?

No output schema exists, so the description carries the return-shape burden and does so thoroughly, naming the metrics and tables returned. With annotations covering safety and the schema covering parameters, nothing an agent needs to call this correctly is missing.

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%, so the baseline is 3. The description goes further by describing the cross-parameter interaction (paths=\"all\" vs \"none\" and trimming to worst maxPaths in both renderings), which is not fully captured in the schema's per-parameter text.

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?

States a specific resource (timing detail for one build) and enumerates exactly what it contains: fMax per clock, total negative slack, worst setup/hold paths with endpoints, and recovery/removal summaries. This distinguishes it cleanly from siblings like gowin_summary and gowin_check.

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?

Gives clear context by explaining what paths="all" versus "none" yield and how the tables are trimmed, which guides invocation. It does not, however, explicitly say when to prefer this tool over siblings such as gowin_check or gowin_summary, so a routing statement is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools