Skip to main content
Glama
Sign In

Vadivam Icons

by io.github.praveenjuge
OverviewDiscussionsAdmin

Search icons

search_icons
Read-onlyIdempotent

Find Vadivam icons by name, synonym tag, or category. Ranked: exact name, then name prefix or word, then tag, then category. Call this before get_icon; never guess icon names.

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
limitNoMaximum results (default 20, max 100).
queryYesWords to match, such as "arrow right", "delete", or "weather". May be empty when category is set.
categoryNoCategory id or title from list_categories, such as "arrows".

Output Schema

NameRequiredDescriptionDefault
queryYes
totalYes
resultsYes
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so safety needs no restating. The description contributes real behavioral value by disclosing the result ranking order — exact name, prefix/word, tag, category — which tells an agent how to interpret ordering and why the first result is likely the best match. Return shape and pagination are left to the output schema.

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?

Three short sentences, zero filler. The core purpose is front-loaded, the ranking detail follows, and the routing directive is placed last where it functions as an operational rule. Every sentence carries information.

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

Completeness5/5

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

With an output schema present, return values need not be described, and annotations fully cover the safety profile. The description supplies the remaining pieces an agent needs — what the tool matches on, how results are ordered, and that it must precede get_icon — for a simple three-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning beyond the schema: it clarifies that 'query' matches three distinct index fields (name, synonym tag, category) rather than being a generic string, and the ranking sentence implies which match types score higher. The 'category' parameter cross-reference to list_categories lives in the schema, not the description.

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?

States a specific verb (find) and resource (Vadivam icons) plus the exact match dimensions: name, synonym tag, and category. The added ranking sentence ('exact name, then name prefix or word, then tag, then category') clearly distinguishes this lookup tool from get_icon, which retrieves one already-known icon.

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?

It gives a strong, actionable rule: 'Call this before get_icon; never guess icon names,' which names the sibling and the condition that selects this tool. It stops short of covering the other siblings, notably suggest_icons, so there is no guidance for choosing between fuzzy suggestion and this search.

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

All Vadivam Icons toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources