oss-cad-mcp

Overview Schema Source Related Servers Discussions Admin

cad_netlist

Read-only

Inspect Yosys JSON netlists to retrieve statistics, modules, cells, nets, and fanout details, or compare netlists for differences.

Instructions

Inspect a Yosys JSON netlist: stats, modules, cells, nets, fanout, or diff.

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

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`job`	No
`path`	Yes
`error`	No
`stats`	No
`action`	Yes
`matches`	No
`modules`	No
`summary`	No
`artifact`	No
`artifacts`	No
`truncated`	No
`module_count`	No
`cells_by_type`	No
`total_matches`	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?

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a read-only inspection tool. However, it does not disclose behavior such as how diff uses the 'other' parameter, error handling for missing or invalid netlists, or default filtering of library/internal modules beyond what the schema already shows.

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 definition is a single front-loaded sentence with no wasted wording. It efficiently names the resource and the available inspection modes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with six action modes and several optional filters, the description is too terse to explain action-specific parameter requirements, especially the role of 'other' in diff and the filtering behavior of module/cell_type. The output schema reduces the need to describe return values, but the input side remains under-specified.

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 lists the action values, but the schema already provides that enum and gives little meaning for the action modes or the other parameters. With schema description coverage reported at 0%, the description does not compensate by explaining path, name, module, cell_type, limit, or the diff-specific 'other' parameter.

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 states a specific verb, 'Inspect', and a specific resource, 'a Yosys JSON netlist', then enumerates the inspection modes. This is clear enough to distinguish the tool from general CAD siblings, though it does not explicitly name those siblings as alternatives.

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 when-to-use guidance, no exclusions, and no mention of alternatives among the many cad_* siblings. The action list implies usage but leaves the agent to infer when netlist inspection is appropriate.

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

Deploy Server