Convert raster images to SVG vector format. Supports color and binary modes with precision controls. Returns raw SVG XML string. FREE. (FREE)
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Vectorization mode | color |
| image | Yes | Base64-encoded PNG/JPEG image | |
| filter_speckle | No | Speckle filter (0-100, higher = fewer small artifacts) | |
| color_precision | No | Color clustering precision (1-10, higher = more colors) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already denote readOnlyHint=true and idempotentHint=true, so the burden on description is lower. The description adds that the tool returns raw SVG XML string, which is useful behavioral context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short (two sentences) and front-loaded with the main purpose. However, the redundant 'FREE. (FREE)' is unnecessary and slightly detracts from conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given full schema coverage and annotations, the description adequately states output format (SVG XML string) and modes. Minor lack of details on input constraints or limitations, but overall sufficient for the complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for all 4 parameters. The description summarizes modes and precision controls but adds no new meaning beyond the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the action 'Convert raster images to SVG vector format' with the specific verb 'convert' and resource 'raster images to SVG', making it clear and distinct from sibling tools like resize_image or remove_background.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for vectorization but lacks explicit guidance on when to use this tool versus alternatives (e.g., 'for vectorization, use this; for other image processing, see siblings'). No 'when to use' or 'when not to use' is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct operation—artwork retrieval, image processing, asset management, watermarking, etc.—with clear descriptions that prevent confusion. Even similar tools like enrich_metadata and get_artwork_oracle are differentiated by depth and purpose.
Tool names follow a consistent verb_noun pattern in snake_case (e.g., get_artwork, remove_background, register_hash). The few non-verb-starting names (compliance_manifest) are standard and do not break the overall pattern.
27 tools is slightly above the typical range but justifiable given the broad domain covering artwork access, image processing, and digital rights. Each tool serves a unique purpose without redundancy.
The tool set covers the full lifecycle: search, retrieve, analyze, edit, save, and verify assets. Gaps are minimal—e.g., no metadata deletion tool—but the core workflows are fully supported, and the inclusion of compliance and provenance tools adds value.