Skip to main content
Glama

export_svg

Destructive

Export a named-net connectivity preview as SVG to review Proteus circuit connections without needing a screenshot or .pdsprj file.

Instructions

Export named-net connectivity preview.svg. This is NOT a Proteus screenshot or .pdsprj.

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

Input Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare destructiveHint=true, but the description does not explain overwrite behavior, output location, permissions, or other side effects. The description adds only artifact-type context beyond the annotations, leaving the destructive nature unexplained.

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 definition is short and front-loaded with the export action, and the negative clarification earns its place by preventing confusion with screenshots. The phrase "named-net connectivity preview.svg" is awkward, but there is little wasted wording.

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 one-parameter tool, the definition still leaves key invocation details missing: the meaning of project and where the SVG is written. With no output schema, the description should do more to explain the artifact and side effects, especially given destructiveHint=true.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter, project, has 0% schema description coverage and is not described in the definition at all. The description does not explain what the project value should be, whether it is a name, path, or identifier, so the parameter remains undocumented.

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 action and artifact: exporting a named-net connectivity SVG preview. It also distinguishes the output from a Proteus screenshot or .pdsprj, though it does not differentiate from sibling export tools such as export_netlist or native_export.

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

Usage Guidelines2/5

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

It gives a narrow negative clarification that this is not a screenshot or .pdsprj, but provides no positive guidance on when to use this tool instead of export_netlist, native_export, or other export siblings. An agent still has to infer the selection criteria.

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