Skip to main content
Glama

3d-cad

svg_path_inspect

Parse SVG command streams into individual geometry segments (M/L/C/Q/A/Z) and compute viewBox and closure metrics.

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

Input Schema

NameRequiredDescriptionDefault
textNoRaw SVG markup or single path d string.
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Parse ... and compute' implies a non-mutating analysis operation, which is useful, but it says nothing about behavior on malformed markup, whether multiple paths in one document are handled, or what the metrics actually contain.

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?

A single dense sentence with no filler, and the operation is front-loaded. It is packed tightly enough that the input forms and metric definitions get squeezed out rather than stated.

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?

With no annotations and no output schema, the description must explain both safety profile and return shape, and it does neither beyond naming 'viewBox and closure metrics'. The missing filePath semantics and the undefined 'closure metrics' leave real gaps for a two-input analysis tool.

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 coverage is only 50%: 'text' is documented while 'filePath' has no schema description. The description never mentions the two accepted input forms (raw markup versus a file path), so it fails to compensate for the uncovered parameter or to clarify precedence when both are provided.

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 and resource: 'Parse SVG <path d="..."> command streams into individual geometry segments (M/L/C/Q/A/Z)' plus 'compute viewBox and closure metrics'. That is far more concrete than a sibling like svg_optimize, though it never explicitly contrasts itself with that or any other sibling.

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 when-to-use or when-not-to-use guidance and no named alternative. An agent must infer from the verb 'inspect' that this is the analysis/diagnostic path rather than the optimize or convert workflow.

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