Get the full SVG markup of an Infyicon icon by id (format: slug_number, e.g. hammer-16_66091 — get ids from search_icons). Returns ready-to-embed SVG code.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Icon id like hammer-16_66091 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of behavioral disclosure. It clearly reveals that the operation returns ready-to-embed SVG markup rather than a URL or binary file. It does not describe error conditions or authentication, but for a simple one-parameter fetch this is acceptable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler: the action and output type are front-loaded, and the second sentence provides the necessary id-format and upstream source guidance. Every part earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter tool with no output schema, the description fully covers what is needed: how to get the id, what the tool returns, and in what form. There is no missing information that would prevent correct usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema already gives the same id format and example. The description adds a useful provenance hint ('get ids from search_icons'), but most parameter meaning is already present in the input schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific action and resource: getting the full SVG markup of an Infyicon icon by id. It includes the id format and names the sibling tool (search_icons) as the source, making it easy to distinguish from get_icon_png and the other siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly tells callers to get ids from search_icons and implies the tool is the right choice when SVG source code is needed. It does not explicitly say to use get_icon_png for raster output, but the context makes that distinction reasonably clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clear, distinct roles: search, list categories, and fetch SVG/PNG by id. Some overlap exists because search_icons already returns SVG and PNG URLs, but get_icon_svg/get_icon_png are clearly meant for direct retrieval by known id.
The naming pattern is generally consistent using verb_noun style: get_icon_svg, get_icon_png, list_categories, search_icons. uicons_lookup deviates slightly by starting with a product name instead of a verb, but it is still understandable and similar in spirit.
Five tools is a well-scoped size for an icon service: search, browse categories, retrieve two format types, and check webfont usage. Each tool has a clear purpose and none feel redundant enough to remove.
The core icon workflow is covered: search, category discovery, SVG/PNG retrieval, and UI-font lookup. Minor gaps exist around category-specific icon listing or richer metadata, but agents can successfully search and fetch icons end-to-end.