Skip to main content
Glama
Sign In
inksmcp

inksmcp

by bhanutpt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

document_save

Save an Inkscape SVG document to a specified path, or overwrite its opened or last-saved location when no path is given.

Instructions

Save the document as Inkscape SVG (to path, or where it was opened/last saved).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "document_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
doc_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It usefully discloses the format written and the fallback target path when none is given, but is silent on overwrite behavior, permissions, and whether an existing file is replaced.

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?

A single front-loaded sentence with zero filler; the format and target-path rule are stated immediately without redundancy.

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?

For a mutation tool with no annotations and no output schema, the description covers the format and default path but omits the role of doc_id and any side effects on existing files, leaving gaps an agent must guess at.

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 0%, so the description must compensate. It clarifies the `path` parameter and its default fallback, adding real meaning, but `doc_id` is never mentioned, leaving one of two parameters undocumented.

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?

States a specific verb (Save) plus resource (document) and the output format (Inkscape SVG), which distinguishes it from sibling document_open/document_create. It is clear what the tool does, though it draws no explicit contrast with siblings like export for other formats.

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 parenthetical implies when path is omitted (save in place to where it was opened/last saved), giving implied usage. It does not state when to prefer this over export, or any preconditions for saving.

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

Deploy Server

Other Tools