Skip to main content
Glama
tathagat22

Plumb (plumb-mcp)

by tathagat22

Plumb · source

plumb_source

Search and fetch design assets from the open web — icons, photos, avatars, illustrations — with parallel provider queries and ranking. Use search mode for metadata or fetch to download the best match.

Instructions

Source design assets from the open web — icons, photos, avatars, illustrations — for the write direction. Queries every provider in parallel (keyless-first: Iconify, Lorem Picsum, DiceBear always work; Unsplash / Pexels / Pixabay activate when their API key is in env) and ranks the results with one scoring function, including pick-the-right-icon-pack so a design uses ONE consistent icon family. Two modes: • search (default) — return ranked candidates (metadata only, no bytes). Cheap; use to see what's available and which icon pack was locked. • fetch — resolve the best match, download its bytes to a local folder, and return the path (+ inline SVG / small data: URI). Never fails: a total miss degrades to a deterministic placeholder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hNoDesired height (photos / placeholders).
wNoDesired width (photos / placeholders).
kindNoConstrain to one asset kind.
modeNo`search` (default) returns ranked candidates; `fetch` downloads the best.
seedNoDeterministic seed for avatars / placeholders.
limitNoMax candidates in search mode. Default 16.
queryYesWhat to look for, e.g. 'rocket launch' or 'shopping cart'.
styleNoPreferred style tags (ranking hint).
aspectNoTarget width/height ratio (ranking hint).
inlineNofetch mode: also return the bytes inline (SVG markup / small data: URI).
weightNoIcon weight preference.
paletteNoBrand hex colors — recolors monotone SVG icons.
minWidthNoMinimum acceptable pixel width.
providerNoRestrict to one provider id (iconify, unsplash, pexels, pixabay, dicebear, picsum, …).
Behavior5/5

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

The description goes beyond annotations by detailing parallel queries, keyless-first providers, ranking logic, mode behavior, and fallback to placeholder. Annotations are minimal (openWorldHint, no readOnly), so the description adds valuable behavioral context.

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 well-structured: opening statement, provider details, mode breakdown. Each sentence adds value, and the format is front-loaded with key information.

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?

Given the complexity (14 parameters, two modes, no output schema), the description covers behavior, modes, providers, and fallback. It lacks explicit output structure for search mode, but is otherwise thorough.

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 100%, so the schema already describes all parameters. The description provides some context (e.g., mode semantics) but does not add significant meaning beyond the schema's descriptions.

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 tool's purpose: sourcing design assets (icons, photos, etc.) from the open web. It distinguishes itself from sibling tools by focusing on asset sourcing with ranking and two modes.

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 explains when to use search (cheap exploration) vs fetch (downloading), and notes provider availability. It does not explicitly mention when to avoid this tool or list alternatives, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tathagat22/plumb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server