Skip to main content
Glama

Inkscape Extension

inkscape_extension
Destructive

Discover, describe, and run installed Inkscape extensions with custom parameters, enabling AI agents to automate SVG processing via GUI or CLI.

Instructions

Discover and invoke any installed Inkscape extension with custom params.

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>"
    },
    "name": "inkscape_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNo
targetNo
operationYes
input_pathNo
wrapper_idNo
output_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the description adds little on safety. It does not warn that running arbitrary extensions can modify or overwrite files, does not distinguish run from run_live (live/interactive side effects), and says nothing about execution failures or side effects.

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?

A single front-loaded sentence with no filler, but the brevity reflects under-specification rather than efficiency. It leaves no room for the operational distinctions the schema demands.

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?

An output schema exists, so return values need not be described, but for a destructive six-parameter tool with zero parameter documentation the description is far too thin. An agent cannot determine which operation to select or how to populate target, input_path, output_path, or wrapper_id.

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?

With 6 parameters and 0% schema description coverage, the description carries the full burden but explains almost nothing: only 'custom params' loosely maps to the params field. The operation enum (list/describe/run/run_live), target, input_path, output_path, and wrapper_id are entirely undocumented, leaving the critical run vs run_live distinction unstated.

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 concrete verb pair and resource: discover (list/describe) and invoke (run) installed Inkscape extensions. It is clear what the tool operates on, though it does not differentiate itself from siblings like inkscape_live, which plausibly overlaps with the run_live operation.

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 guidance on when to choose this tool over inkscape_live or inkscape_file, no prerequisites, and no mention of when not to use it. 'with custom params' hints at extensibility but offers no selection criteria between the four operations.

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