Skip to main content
Glama

Inkscape Analysis

inkscape_analysis
Read-onlyIdempotent

Inspect SVG structure, quality, dimensions, objects, and statistics to validate files before editing. Use read-only analysis to catch issues and confirm SVG properties.

Instructions

INKSCAPE_ANALYSIS — Inspect SVG structure, stats, quality, and dimensions (read-only).

PORTMANTEAU RATIONALE: Analysis calls are grouped so agents can validate before mutating.

Operations: quality, statistics, validate, objects, dimensions, structure.

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

Input Schema

NameRequiredDescriptionDefault
operationYesAnalysis mode (Literal).
input_pathYesSVG file to analyze.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the description's '(read-only)' adds little. It does add the workflow context that analysis exists to validate state before mutation, which is genuine value. But it does not describe cost, per-operation behavior, or failure modes for malformed SVG input, which would be useful beyond the annotations.

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 purpose is front-loaded in the first line, followed by a short rationale and an operation list. There is minimal waste, though the 'PORTMANTEAU RATIONALE' label is meta-commentary that could be folded into a plain sentence. It is appropriately sized for a two-parameter dispatcher tool.

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?

An output schema exists, so return values need not be explained. However, this is a six-mode dispatcher and the description never states what any individual operation produces or requires, leaving an agent unable to pick a mode confidently. For a portmanteau tool of this breadth, the definition is minimally adequate but has a clear gap in operation-level semantics.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters (operation enum and input_path) are already documented, establishing a baseline of 3. The description merely repeats the enum values without explaining what distinguishes 'quality' from 'validate' or 'structure' from 'objects'. No additional semantic meaning is contributed beyond the schema.

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 gives a specific verb (inspect) and resource (SVG) and enumerates the six analysis modes: quality, statistics, validate, objects, dimensions, structure. It is clearly a read-only inspection tool. It does not differentiate itself from siblings such as inkscape_file or inkscape_metadata, which likely also read SVG content, so it falls short of a 5.

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?

The 'PORTMANTEAU RATIONALE' line implies usage ('agents can validate before mutating'), which is a useful workflow hint. However, there are no explicit when-not-to-use conditions, no guidance on choosing among the six operations, and no routing to alternative tools for tasks this one doesn't cover. Usage is implied rather than stated.

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