asset-finder-mcp

search_vectors

Search and retrieve downloadable SVG vectors and illustrations from a repository of 500,000+ open-licensed files, including license information.

Instructions

Search for SVG vectors and illustrations from SVG Repo (500,000+ open-licensed SVGs). Returns downloadable SVG files with license information.

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": {
      "query": "<query>"
    },
    "name": "search_vectors"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max results (default 15)
`query`	Yes	Search term (e.g. 'arrow', 'chart graph', 'phone mobile')
`license`	No	Filter by license: cc0, cc-by, cc-by-sa, cc-by-nc

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 5, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the transparency burden. It discloses that the tool returns downloadable SVG files with license information, but it omits details like output format, pagination behavior, or error handling. This is moderate disclosure.

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 states the primary action and result. It contains no filler, redundancy, or unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 3-parameter search tool with no output schema, the description covers purpose, source, and return type (downloadable SVG files with license info). It lacks detailed output structure, but is sufficiently complete for basic invocation.

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?

The input schema provides 100% parameter coverage with descriptions, so the baseline is 3. The tool description adds no extra parameter semantics beyond the schema, only mentioning license information in the return context.

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 clearly states the action 'Search' and resource 'SVG vectors and illustrations from SVG Repo', with scale and licensing context. It distinguishes from siblings like search_icons and search_logos by specifying a different asset category and source.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when to use this tool (when searching for SVG vectors/illustrations from SVG Repo), but it does not explicitly mention exclusions or alternative sibling tools. This aligns with 'clear context, no exclusions'.

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

Deploy Server