Noun MCP Server

search_collections

Find relevant icon sets by searching Noun Project collections with a query term.

Instructions

Search Noun Project collections (icon sets). Service call — cheaper than get_icon/download_icon.

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

Input Schema

Name	Required	Description
`limit`	No	Maximum number of results
`query`	Yes	Collection search term
`next_page`	No	Token for next page
`prev_page`	No	Token for previous page

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 24, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that this is a 'service call' and cheaper than download-related tools, but it does not disclose whether results are paginated, what the response shape is, whether authentication is required, or other operational behavior.

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 front-loads the core purpose and adds a concise cost-related note. Every part earns its place, and there is no redundant or vague filler.

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

Completeness3/5

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

The description is adequate for a basic search tool but incomplete without output schema or annotations. It does not explain what the returned collection data looks like, how pagination should be driven via next_page/prev_page, or any usage caveats.

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 description coverage is 100%, so the parameters are already documented. The description adds no extra meaning about query syntax, limit defaults, or pagination token usage, placing it at the baseline.

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 states a specific verb and resource: 'Search Noun Project collections (icon sets).' This clearly differentiates it from retrieval/download siblings like get_icon and download_icon, and the '(icon sets)' qualifier separates it from search_icons.

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 it is used for searching collections rather than icons, but it does not explicitly state when to use this tool versus search_icons, get_collection, or icon_autocomplete. The 'cheaper than get_icon/download_icon' note adds some cost-based context but not clear selection criteria.

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

Deploy Server