Skip to main content
Glama

native_preview

Destructive

Render a new SVG preview from calibrated native component, pin, wire, and junction geometry, producing a reconstructed vector view instead of a screenshot.

Instructions

Render an SVG from actual calibrated native component/pin/wire/junction geometry. This is a reconstructed vector preview, not a screenshot. New output only.

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": {
      "path": "<path>"
    },
    "name": "native_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
outputNo

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 already declare readOnlyHint=false and destructiveHint=true, so the read/write profile is technically covered, but the description reads like a harmless renderer and never says what is destroyed or overwritten, or what happens when the output target already exists. It does add one genuinely useful behavioral fact - that the SVG is a reconstructed vector preview rather than a pixel screenshot - but the destructive character implied by annotations is left unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the first two sentences are efficient and non-redundant. The trailing 'New output only' is cryptic filler that costs space without conveying a clear rule.

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?

With no output schema, two undocumented parameters, and no explanation of why a preview tool is destructive, the description is thin for the operation it wraps. An agent could call it correctly only by guessing what path and output should contain and whether existing files are at risk.

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?

Schema description coverage is 0%, so the description must carry the burden for 'path' and 'output' and it largely does not. Only an indirect hint exists ('from ... geometry' suggests path is a source file, and 'Render an SVG' suggests output is the destination), with no format, extension, or overwrite semantics given.

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?

Names a specific verb and output artifact ('Render an SVG') and pins down the source ('actual calibrated native component/pin/wire/junction geometry'), plus a disambiguation from screenshots. It stops short of distinguishing itself from export-flavored siblings such as export_svg or native_export, so an agent still has to guess which produces the 'real' deliverable.

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?

There is no when-to-use or when-not-to-use guidance and no alternatives named among the many export/preview siblings. 'New output only' is the closest thing to a usage constraint but its meaning is not spelled out, so the agent must infer the routing rule.

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