oss-cad-mcp

Overview Schema Source Related Servers Discussions Admin

cad_check

Read-only

Parses, lints, or elaborates Verilog, SystemVerilog, or VHDL sources and returns normalized diagnostics to catch syntax and semantic issues before simulation or synthesis.

Instructions

Parse, lint, or elaborate HDL sources and return normalized diagnostics.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request": "<request>"
    },
    "name": "cad_check"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`job`	Yes
`top`	No
`error`	No
`level`	Yes
`counts`	No
`engines`	No
`summary`	No
`warnings`	No
`artifacts`	No
`hierarchy`	No
`unresolved`	No
`diagnostics`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that diagnostics are returned normalized, which is useful behavioral context, but it says nothing about engine selection, timeout behavior, or partial-failure semantics for a tool that shells out to slang/verilator/iverilog/ghdl.

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?

A single well-formed sentence with no filler and the action front-loaded. It is tight, though the density means several invocation-relevant details are omitted rather than merely compressed.

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?

An output schema exists, so return values need no explanation, and annotations cover safety. However, for a tool with engine selection, timeouts, and multi-language source sets, the description leaves too much of the invocation contract implicit.

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

Parameters2/5

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

With schema description coverage reported at 0%, the description must carry parameter meaning, and it largely does not: engines, timeout_s, defines, filelist, and include_dirs are never mentioned. Only the level parameter is indirectly illuminated by the parse/lint/elaborate verb list.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names three concrete actions (parse, lint, elaborate) against a concrete resource (HDL sources) plus the outcome (normalized diagnostics), so an agent can distinguish this from cad_synthesize or cad_simulate. It stops short of naming a sibling to route away from, which keeps it from a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The three verbs imply the tool's role in a check flow, but the agent must infer that selection from general HDL knowledge rather than from the text.

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

Deploy Server