oss-cad-mcp

Overview Schema Source Related Servers Discussions Admin

cad_tool_run

Destructive

Runs an allowlisted OSS CAD Suite binary with custom arguments for controlled HDL workflows such as linting, simulation, synthesis, and formal verification.

Instructions

Run an allowlisted suite binary with argv. Prefer high-level workflows.

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

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`job`	Yes
`argv`	No
`tool`	Yes
`error`	No
`summary`	No
`artifacts`	No
`exit_code`	No
`duration_s`	No
`started_at`	No
`stderr_tail`	No
`stdout_tail`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

B3.1/5.0

Behavior3/5

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

The annotations already declare destructiveHint=true and openWorldHint=false, so the safety profile is known. The description adds the useful constraint that only allowlisted binaries are accepted, which is behavior beyond the schema, but it says nothing about what allow_unsafe unlocks or what happens on timeout — material for a destructive tool.

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?

Two short sentences with no filler, and the fallback guidance is placed where a reader will see it. It is efficiently written, though the brevity comes at the cost of substance rather than being tight and complete.

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 destructive, nested-parameter tool with zero schema description coverage, two sentences are not enough. The output schema covers return values, but the safety-relevant inputs (allow_unsafe, timeout_s, stdin) and the allowlist boundary are never described.

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?

Schema description coverage is 0%, so the description must carry parameter meaning, and it only hints at 'argv' (args). The nested request fields — tool, cwd, stdin, timeout_s, and especially allow_unsafe with its safety implications — are left entirely unexplained.

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 verb ('Run') and resource ('allowlisted suite binary with argv'), so an agent knows this is a generic binary-execution escape hatch. It does not name which sibling workflow tools to prefer instead, but the action itself is unambiguous.

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?

'Prefer high-level workflows' signals that this is a fallback rather than a first choice, which is real routing guidance. However it names no specific alternative and gives no conditions for when the low-level path is actually justified.

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

Deploy Server