Skip to main content
Glama

3d-cad

svg_optimize

Minify and optimize SVG markup by stripping XML comments, metadata, editor namespaces, empty groups, and rounding float precision.

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": "svg_optimize"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoRaw SVG markup.
filePathNo
precisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden. It discloses which markup constructs are stripped, which hints at lossiness, but says nothing about whether the source file is overwritten, whether the result is returned as a string, or whether anything is written to disk when filePath is supplied. For a transforming tool whose output behavior is invisible from the schema, that is a substantial gap.

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 that names the operation first and then the specifics, with no filler or redundant restatement of the tool name.

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?

There is no output schema and no annotations, so the description must cover both behavioral and return-value ground. It never says what the caller gets back (optimized markup? a file path? a savings report?) and leaves the text/filePath precedence unresolved, which is not enough for a three-parameter transformation tool whose effects may be on disk.

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 coverage is only 33% ('text' is the only documented parameter). The description partially compensates by explaining that float precision gets rounded, giving 'precision' real meaning. However, 'filePath' is left entirely unexplained in both schema and description, so an agent cannot tell whether it is an input source, an overwrite destination, or both.

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 ('Minify and optimize') with a specific resource ('SVG markup') and enumerates the transformations performed (XML comments, metadata, editor namespaces, empty groups, float precision). That is far more concrete than 'process an SVG'. It does not explicitly differentiate itself from the sibling svg_path_inspect, but the operation described is clearly distinct from path inspection.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no indication of when optimization is appropriate. Notably it never explains the relationship between the two input modes (raw markup via 'text' vs. a 'filePath'), which is the primary decision an agent faces when invoking it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources