Skip to main content
Glama

Inkscape Metadata

inkscape_metadata
Idempotent

Read or write Dublin Core metadata in an SVG's rdf:RDF block, letting AI agents get or set the title, creator, description, rights, and keywords of Inkscape files.

Instructions

Read/write Dublin-Core metadata in the SVG's rdf:RDF block.

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

Input Schema

NameRequiredDescriptionDefault
valueNo
operationYes
input_pathYes
output_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the agent knows this is a non-destructive idempotent write-capable tool. The description adds the location of the metadata (the RDF block), but it does not explain that set operations require a value, how output_path affects writes, or what happens when output_path is omitted.

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?

The description is a single front-loaded sentence with no filler or redundant wording. It is appropriately sized for its limited content, though the conciseness comes at the cost of missing detail elsewhere.

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?

The tool has four parameters with 0% schema description coverage and an output schema, but the description does not compensate for the missing parameter guidance. It lacks essential operational details such as when set operations write to disk, what value does, and how output_path behaves, leaving the agent to infer too much.

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 of explaining the four parameters, yet it only implies a get/set duality. It does not explain what value means for set operations, what input_path and output_path do, or how the operation enum maps to read versus write behavior.

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 uses a specific verb pair (read/write) and a specific resource (Dublin-Core metadata in the SVG's <rdf:RDF> block). It is clear what the tool operates on, though it does not explicitly distinguish itself from any of the sibling Inkscape tools.

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?

The description says read/write metadata but gives no guidance on when to choose get versus set operations, when to supply output_path, or when another tool might be more appropriate. It contains no when-to-use or when-not-to-use conditions.

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