Skip to main content
Glama

Search icons

search_icons
Read-onlyIdempotent

Suggest icon names (best-effort web search). In app code prefer lucide-react or inline SVG.

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

Input Schema

NameRequiredDescriptionDefault
queryYes
project_idNoProject id (or use session from use_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, non-destructive and openWorld behavior, so the safety profile is covered. The description adds one genuinely useful trait — "best-effort" — warning that results may be unreliable or incomplete. It says nothing about how many suggestions come back or whether results are cached/fresh.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the function and followed by the caveat; nothing is wasted. It is arguably over-terse for a search tool, but there is no filler or redundancy.

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?

For a simple two-parameter read-only search there is little that must be said, and annotations plus the partial schema cover most of it. However, with no output schema the description should at least sketch the shape of the suggestion list, and query format remains unexplained, leaving a real gap.

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?

With only 50% schema description coverage, the description needs to explain the undocumented parameters, and it does not. It never says what form "query" should take (icon name, style keyword, semantic concept) or what project_id scopes; the only hint is the implicit idea of an icon-name search.

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?

The description states a specific verb and resource ("Suggest icon names") plus the underlying mechanism ("best-effort web search"), so an agent knows exactly what it returns. It does not differentiate itself from siblings like web_search or search_photos, but the icon-specific output makes the intent unambiguous.

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?

It gives one negative rule of thumb: "In app code prefer lucide-react or inline SVG" — a useful signal that this tool is not for design-time coding decisions. There is no positive guidance on when to reach for this versus web_search, and no prerequisites or exclusions beyond that single caveat.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources