oss-cad-mcp

by ChalkCalliope

Overview Schema Source Related Servers Discussions Admin

Python

Local

cad_synthesize

Synthesize HDL designs with Yosys to produce cell statistics and a JSON netlist for downstream analysis.

Instructions

Synthesize HDL with Yosys and return cell statistics and a JSON netlist.

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_synthesize"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`job`	Yes
`top`	No
`error`	No
`stats`	No
`target`	Yes
`netlist`	No
`summary`	No
`warnings`	No
`artifacts`	No
`cells_by_type`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Beyond the annotations' basic safety profile, the description adds the concrete synthesis engine and the two kinds of results returned. It does not explain possible filesystem or project side effects, failure and timeout behavior, or project-configuration dependencies, so the behavioral context remains limited.

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 single sentence is front-loaded with the action and tool, then concisely states the returned results. Every clause contributes useful information, with no filler or repetition.

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?

Together with the structured schema, annotations, and output schema, the description is sufficient to understand the basic operation and inspect the invocation requirements. For a configurable synthesis tool, however, it omits usage boundaries, source and project prerequisites, and meaningful side-effect context.

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?

The description establishes that the input domain is HDL but adds no guidance about the required request payload or options such as source, top, target, abc9, flatten, and timeout_s. With schema description coverage reported at 0%, it does little to compensate, although the nested schema's property names, enums, and defaults still provide some information.

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 gives a specific operation and resource—synthesizing HDL with Yosys—and identifies the cell statistics and JSON netlist produced. It does not explicitly distinguish this synthesis step from related build, netlist, or generic tool-running siblings.

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?

Usage is implied: choose it when HDL synthesis and synthesis statistics or a netlist are needed. There is no explicit guidance about prerequisites, when not to use it, or which alternative tool fits broader or different workflows.

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

Deploy Server