Skip to main content
Glama
Sign In
infyicon-mcp

infyicon-mcp

by krupalghori44-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Get popular icons

get_popular_icons
Read-onlyIdempotent

Browse popular Infyicon icons without a search query. Get up to 30 featured icons with IDs, names, styles, and URLs for quick selection and download.

Instructions

Return up to 30 popular/featured Infyicon icons (ids, names, styles, page/SVG/PNG URLs) without a search query - use when the user just wants "a nice icon" or a starting set and has not named a subject. Use search_icons instead when the user describes a subject, and get_related_icons instead when they already have an icon and want variations. Read-only, no auth; always returns results (never errors on empty input). Free with attribution to infyicon.com.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 12, max 30)
styleNoOptional: restrict to one style

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description goes further by adding 'no auth', 'always returns results (never errors on empty input)', and 'Free with attribution to infyicon.com', which are not available in the annotations. This meaningfully increases the agent's understanding of safety and side effects.

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 front-loaded with the core purpose in the first sentence, followed by usage guidance, and finally behavioral/legal notes. Every sentence carries necessary information—no filler or repetition. Three sentences is appropriate for the tool's complexity.

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 no output schema, the description explains the return shape by listing fields (ids, names, styles, URLs). It also covers usage conditions, auth requirements, error behavior, and attribution. For a 2-param read-only tool with full annotation coverage, this is complete.

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?

The input schema already provides 100% coverage, describing both limit and style with constraints and defaults. The description adds 'up to 30' which matches the schema's max, and mentions 'without a search query' to clarify there is no query param, but this is already evident from the schema. No new semantic meaning is added beyond the schema.

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 states a specific verb ('Return') and resource ('popular/featured Infyicon icons') with concrete output fields (ids, names, styles, URLs). It also distinguishes this tool from search_icons and get_related_icons, making it clear what this tool is not for.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use this tool: 'when the user just wants "a nice icon" or a starting set and has not named a subject.' It also names alternatives with their conditions: search_icons for described subjects, get_related_icons for variations from an existing icon. No inference needed.

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

Deploy Server

Other Tools