Skip to main content
Glama

Inkscape System

inkscape_system
Idempotent

Check Inkscape server status, diagnostics, version, and configuration, or list and run extensions for interactive and headless workflows.

Instructions

INKSCAPE_SYSTEM — Server/Inkscape status, help, diagnostics, version, extensions.

PORTMANTEAU RATIONALE: Operational and introspection calls stay in one discoverable tool.

Operations: status, help, diagnostics, version, config, list_extensions, execute_extension.

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

Input Schema

NameRequiredDescriptionDefault
operationYesSystem subcommand (Literal).
input_fileNo
output_fileNo
extension_idNoExtension to run for execute_extension (use list_extensions to discover ids). input_file is also required; output_file defaults to overwriting input_file. extension_params carries the extension's own options — call inkscape_extension(describe) for its schema.
extension_paramsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the description's burden is the extra context, and it adds none. It never discloses that status/help/version are pure reads while execute_extension runs external extension code, nor that output defaults to overwriting input_file. With no annotations these gaps would be fatal; even with them, the mixed read/write nature of the seven operations is left opaque.

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 operation list is front-loaded and the whole definition is two short blocks with no padding. The 'PORTMANTEAU RATIONALE' line is meta-commentary aimed at a maintainer rather than an agent, but it costs little.

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?

This is a seven-operation multiplexer with a 5-parameter, 40%-covered schema, and the description never maps parameters to operations or explains which calls mutate state. An output schema exists so return values need not be described, but the per-operation parameter applicability gap is substantial for this complexity.

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 coverage is only 40%, so the description should compensate, but it explains no parameters at all. It does not indicate that input_file/output_file/extension_params apply only to execute_extension while the other six operations ignore them, which is the single most useful thing it could say; the only semantic help for extension_id lives in the schema, not the description.

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 names the resource (server/Inkscape status, help, diagnostics, version, extensions) and enumerates seven concrete operations that match the enum exactly, so an agent knows this is the operational/introspection tool rather than analysis, gradient, or file work. It stops short of explicitly differentiating itself from every sibling, but the operational framing is clear.

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?

'Operational and introspection calls stay in one discoverable tool' implies the class of task that belongs here, and the operation list implies when each subcommand applies. There is no explicit when-not guidance or routing to siblings, and the useful hint about calling inkscape_extension(describe)/list_extensions appears only inside the schema, not the description.

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