Skip to main content
Glama

export_netlist

Destructive

Exports a project's connectivity as a portable semantic netlist.json for analysis or transfer, not a Proteus native file. Use it to capture circuit nets and pins in a reusable format.

Instructions

Export portable semantic netlist.json, NOT an importable Proteus native file.

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": {
      "project": "<project>"
    },
    "name": "export_netlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, which is counterintuitive for something called 'export', yet the description does nothing to explain what is destroyed or overwritten, where the file is written, or what permissions are needed. It does add genuine context beyond annotations by characterizing the output as portable semantic JSON rather than an importable native file, which is why this is not lower.

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?

A single front-loaded sentence with no filler and the key distinction placed immediately. It is tight but arguably too spare for a destructive-flagged export operation, leaving important qualifications unstated.

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 carrying destructiveHint=true and no output schema, an agent needs to know what is written, where, and whether existing files are overwritten; none of that is present. The undocumented 'project' parameter compounds the gap, so the definition is not complete enough to invoke safely on its own.

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?

There is one parameter ('project') at 0% schema description coverage, so the description carries the full burden of explaining it and says nothing about what 'project' means, whether it is a name, id, or path. The export target location and format options are likewise unaddressed.

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?

States a specific verb ('Export') and a specific artifact ('portable semantic netlist.json'), then adds a negative scope clause ('NOT an importable Proteus native file') that separates it from the native_export family of siblings. The one gap is that it never names the sibling an agent should pick instead for a native file.

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 'NOT an importable Proteus native file' clause implies when this tool is inappropriate and therefore when a native export sibling is preferred, but the guidance is only implied through negation. There is no explicit 'use native_export when you need an importable file' routing statement.

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