Skip to main content
Glama

Inkscape Gradient

inkscape_gradient
Destructive

Edit SVG gradients in a file by adding, removing, or recoloring stops and converting linear gradients to radial or radial to linear.

Instructions

Add/remove/recolor gradient stops; convert linear↔radial (headless — edits a file).

Preferred over hand-writing gradient SVG for file/headless work. NOT a live tool: it reads/writes a file, so for gradients on an OPEN document use inkscape_live edit_xml instead (avoids a reopen).

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": {
      "operation": "<operation>",
      "input_path": "<input_path>",
      "output_path": "<output_path>"
    },
    "name": "inkscape_gradient"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationYes
input_pathYes
stop_colorNo
gradient_idNo
output_pathYes
stop_offsetNo
stop_opacityNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds meaningful context beyond the annotations: the tool is file-based, reads and writes files, and choosing it on an open document forces a reopen. It does not clarify whether input_path is modified in place or whether output_path may be overwritten, which matters given destructiveHint=true.

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: capability and file model first, then the routing/exclusion guidance. Every clause earns its place with no filler.

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

Completeness3/5

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

Strong on purpose and routing, but incomplete for a 7-parameter, fully undocumented, destructive file-writing tool -- an agent still lacks per-parameter semantics and any statement about overwrite behavior of input_path/output_path. The existing output schema relieves it of explaining return values.

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% across 7 parameters, so the description must carry the load -- yet it never explains gradient_id requirements, stop_color format, stop_offset units, or which parameters apply to which of the six operations. Only a loose mapping to the operation enum is implied.

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?

States specific verbs and resource -- add/remove/recolor gradient stops, convert linear↔radial -- plus the key scope qualifier '(headless — edits a file)'. An agent can immediately distinguish this from the live-editing sibling.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('preferred over hand-writing gradient SVG for file/headless work') and when-not ('NOT a live tool... for gradients on an OPEN document use `inkscape_live` `edit_xml`'), naming the alternative and the reason (avoids a reopen). Nothing is left to inference.

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