Skip to main content
Glama

make_sheet

Move parts into a new sub-sheet and replace them with an instance in one change, turning boundary nets into ports so the netlist stays intact.

Instructions

Move parts into a new sub-sheet .sheet.tsx and put an instance of it in their place, as ONE change. Each net crossing the boundary becomes a port of that name, so the netlist stays the same.

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": {
      "file": "<file>",
      "name": "<name>",
      "parts": "<parts>"
    },
    "name": "make_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesCircuit file
nameYese.g. PowerStage
partsYese.g. ["U2", "C4"]
renameNoNumber the parts from 1
instanceNoDefault e.g. PowerStage1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/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 well: it discloses atomicity ('as ONE change') and the key invariant that each boundary-crossing net becomes a port so the netlist is unchanged. It stops short of covering failure modes such as name collisions or whether the original file is modified in place.

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?

Two tight sentences with the action and its guarantee front-loaded; every clause (atomic change, port-per-net, netlist preserved) carries information an agent needs. No filler.

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

Completeness5/5

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

For a 5-parameter mutation tool with no annotations and no output schema, the description covers the essential what, the atomicity, and the netlist-preservation guarantee that determines whether the call is safe. Remaining gaps (return value, error behavior) are minor and largely out of scope here.

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 100%, so baseline is 3, but the description adds real meaning: it ties 'name' to the generated <name>.sheet.tsx filename and explains that the instance replaces the moved parts, clarifying how 'instance' and 'parts' relate. It does not clarify 'rename' or the default instance naming beyond the schema's own example.

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?

Names a specific verb and resource (move parts into a new sub-sheet named <name>.sheet.tsx) and states the resulting state (an instance left in their place). This is concrete enough to distinguish it from sibling tools like describe_sheet or module_info, which read or inspect rather than restructure.

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 description implies when the tool applies (refactoring parts into a reusable sub-sheet) and notes it happens as ONE atomic change, but it never states when to prefer it over alternatives such as edit_circuit or when not to use it. Usage is inferable rather than prescribed.

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