Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

search_icons

Read-onlyIdempotent

Find local SVG icon names and families by query, then use the returned pack and name with get_icon to retrieve the exact icon.

Instructions

Search local SVG names and families. Use the exact returned pack and name with get_icon.

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": "search_icons"
  }
}

Input Schema

NameRequiredDescriptionDefault
packNo
limitNo
queryNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds that results are local and that returned pack/name values must be reused verbatim, which is useful. It does not mention pagination (limit/offset) or what the result set looks like beyond pack and name.

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?

Two short sentences, front-loaded with the action and followed by the handoff instruction. Nothing is wasted.

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 four undocumented parameters, no output schema, and no paging guidance, an agent cannot tell how to scope a large search or how to page through results. The handoff to get_icon is the only workflow detail supplied.

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 description coverage is 0% for four parameters, so the description carries the whole burden. 'Names and families' hints at what query matches and 'returned pack' hints at the pack filter, but limit and offset are entirely unexplained and no parameter format or default is given.

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: searching local SVG icon names and families. The second sentence distinguishes it from the retrieval sibling get_icon, so an agent can tell search from fetch without opening either schema.

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?

Gives a clear downstream step (use the exact returned pack and name with get_icon), which implies this is the discovery step before retrieval. It says nothing about when not to use it, or how it relates to other lookup siblings such as list_icon_packs or search_inspirations.

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