Skip to main content
Glama
Sign In
imagetosvg-mcp

imagetosvg-mcp

by ujo78
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Inspect SVG

inspect_svg

Return SVG dimensions, viewBox, and detailed layer information including id, tag, fill, stroke, pathCount, and bounding box for inspection and editing.

Instructions

Return SVG dimensions, viewBox, and the list of addressable layers (id, tag, fill, stroke, pathCount, bbox).

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": {
      "svg_path": "<svg_path>"
    },
    "name": "inspect_svg"
  }
}

Input Schema

NameRequiredDescriptionDefault
svg_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/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 clearly states the output, implying a read-only operation with no side effects. However, it does not mention error handling or file validation.

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 sentence that efficiently conveys the tool's purpose and output. Every word adds value; no redundancy.

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 description fully details the output but neglects the input parameter entirely. Given the tool's simplicity, it is incomplete as it fails to describe how to call the tool.

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

Parameters1/5

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

The schema coverage is 0%, yet the description does not explain the 'svg_path' parameter. It omits any mention of the input, leaving the agent without guidance on how to specify the SVG file.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the tool returns SVG dimensions, viewBox, and addressable layers with specific fields. This clearly distinguishes it from sibling tools like edit_svg or render_svg, which have different purposes.

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 description implies usage for inspection, but provides no explicit guidance on when to use it versus alternatives. There are no exclusions or conditions mentioned, leaving the agent to infer.

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