klayout-mcp

by aycandv

Overview Schema Source Related Servers Discussions Admin

Python

Local

extract_markers

Retrieve violation markers from a completed DRC run, optionally with PNG crops around each marker for review.

Instructions

Return the violation markers from a run_drc_script run.

Args: session_id: Session returned by open_layout. run_id: Run id returned by run_drc_script. include_crops: Also render a PNG crop around each marker. crop_size_um: Crop window size in microns: {"x": float, "y": float} (default 20x20).

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": {
      "session_id": "<session_id>",
      "run_id": "<run_id>"
    },
    "name": "extract_markers"
  }
}

Input Schema

Name	Required	Description	Default
`run_id`	Yes
`session_id`	Yes
`crop_size_um`	No
`include_crops`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.3Sep 13, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the optional side effect that `include_crops` renders a PNG crop and gives the default crop window (20x20 um), which is real behavioral context beyond the schema. It does not state read-only/safety profile, permission requirements, or behavior on an unknown run_id.

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?

The purpose sentence is front-loaded and the parameter notes are terse and each earn their place. The Args block is slightly formulaic but contains no filler.

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

Completeness4/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-value description is unnecessary, and the description covers purpose, all parameters, and the optional crop rendering. It would be fully complete with a note on what happens when the referenced run is missing or whether extraction is read-only.

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 description coverage is 0%, so the description must compensate, and it does: it documents all four parameters, gives the provenance of session_id (`open_layout`) and run_id (`run_drc_script`), and clarifies crop_size_um as an {x, y} micron window with a default. Only the exact units/format edge cases are left thin.

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 verb and resource ('Return the violation markers') and scopes it to a run produced by the sibling `run_drc_script`. An agent can distinguish this from query_region, measure_geometry, or run_drc_script itself without opening any schema.

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?

The phrase 'from a `run_drc_script` run' implies the prerequisite that a DRC run must exist and that run_id/session_id come from `open_layout` and `run_drc_script`, which is useful. However, there is no explicit when-to-use/when-not guidance or named alternative among the many siblings.

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

Deploy Server