Skip to main content
Glama

Search icons

search_icons
Read-only

Find icons for a meaning or a UI action ("delete", "turn camera off", "invite user"). Ranked by the same engine as gentleface.com: names, meanings, synonyms and user phrasings, with notes on which icon to prefer. Search once per meaning you need.

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
limitNo
queryYesWhat the icon should mean or do, in plain words

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: results are ranked by name, meaning, synonyms and user phrasings, and include notes on which icon to prefer — which tells the agent the output is ordered and opinionated, not a flat match list. It omits any mention of how many results come back by default or how the limit affects ranking.

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?

Three short sentences, purpose front-loaded, examples early, and the ranking/provenance note kept brief. The 'same engine as gentleface.com' clause is the only soft-marketing phrasing that could be trimmed without loss.

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 two-parameter read-only search tool with annotations covering safety and no output schema, this is nearly complete: it conveys what to pass in, how results are ranked, and that preference notes come back. The only gap is behavioral detail on the limit parameter and relaxed vs strict matching.

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 50%: query is documented, limit is not. The description reinforces the query intent with natural-language examples ('turn camera off'), which is slightly more helpful than the schema's 'in plain words', but it never addresses limit or its interaction with result quality, leaving that parameter undocumented everywhere.

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 ('Find icons') plus what the input represents ('a meaning or a UI action') with three concrete examples ('delete', 'turn camera off', 'invite user'). It does not distinguish itself from siblings such as get_icons or get_icon, so an agent must infer that this is the semantic/natural-language search entry point rather than a lookup by id or category.

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 line 'Search once per meaning you need' gives real usage guidance about how to batch queries rather than iterating. However, there is no explicit statement of when to prefer this over get_icons or list_categories, and no guidance on what to do when results are unsatisfying.

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.