klayout-mcp

Overview Schema Source Related Servers Discussions Admin

set_view

Configure the default render view for a session to control how subsequent renders appear. Specify box, cell, or layers; omitted arguments retain current values.

Instructions

Set the session's default render view used by later render_view calls.

Omitted arguments keep their current value. Changing cell without a box auto-fits the view to that cell.

Args: session_id: Session returned by open_layout. box: View window in microns: {"left", "bottom", "right", "top"}. cell: Cell to render. layers: Visible layers as [{"layer": int, "datatype": int}].

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>"
    },
    "name": "set_view"
  }
}

Input Schema

Name	Required	Description	Default
`box`	No
`cell`	No
`layers`	No
`session_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.3Sep 13, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses partial-update semantics ('Omitted arguments keep their current value'), an auto-fit side effect, and that the setting persists for later render_view calls. It omits error/permission behavior and what happens if session_id is stale, which a mutation tool ideally covers.

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?

Front-loaded with the core purpose, followed by concise behavioral notes and a tidy Args list. Every sentence carries information, though the Args block is somewhat verbose relative to the schema.

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 values need not be explained, and the description covers the mutation semantics and parameter formats adequately for a 4-parameter stateful tool. Remaining gaps (persistence scope, failure modes) are minor against the schema and output schema already provided.

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 coverage is 0%, so the description must compensate, and it largely does: it documents all four parameters, gives box's key set and micron units, and specifies the layers shape [{layer, datatype}]. Minor gaps remain, such as whether box requires all four keys and the null/default meaning.

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 and resource ('Set the session's default render view') and ties it to the sibling tool render_view, so an agent can distinguish configuring the view from actually rendering it. It is clear, though it does not explicitly say 'use set_view rather than render_view when configuring'.

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

Usage Guidelines4/5

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

It establishes clear context via its relationship to later render_view calls and gives conditional rules: omitted arguments keep current values, and changing cell without a box auto-fits. It stops short of stating when not to use this tool, so it lacks explicit exclusions.

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

Deploy Server