Digche Icons

Find a Digche replacement

find_replacement

Find and rank Digche replacements for an icon from Lucide, Heroicons, Material Symbols, Font Awesome, or another library. Include the UI context for a more useful match; that context may be written in English or Persian.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	1 to 10 candidates.
`context`	No	Functional UI context, for example Back button in mobile navigation.
`sourceIcon`	Yes	Original component or icon name, for example ArrowLeft.
`sourceLibrary`	No
`preferredStyle`	No		Linear

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedAug 17, 2026
- addedInput schema / properties / limit / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]
```
- removedInput schema / properties / limit / default
```
Removed value: -5
```
- addedInput schema / properties / limit / description
```
Added value: +"1 to 10 candidates."
```
- removedInput schema / properties / limit / maximum
```
Removed value: -10
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- removedInput schema / properties / limit / type
```
Removed value: -"integer"
```
First observedAug 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that candidates are found and ranked and that context improves match quality. It does not disclose ranking criteria, failure behavior, or output format, but for a read-only lookup the core behavior is reasonably clear.

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 two sentences with no filler. The core purpose is front-loaded, and the usage hint about UI context is packed into the second sentence without 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?

The tool has five parameters, no output schema, and no annotations, so the description could do more. It leaves the return shape and ranking criteria unspecified and does not distinguish itself from recommend_icons. Still, the schema covers parameter semantics well enough for a basic call.

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 description coverage is 60%, so the description partially compensates. It adds meaning to context (functional UI context, English or Persian) and clarifies that sourceIcon/sourceLibrary refer to icons from common icon libraries. It does not add value for limit or preferredStyle beyond what the schema already provides.

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 ('find and rank'), a clear resource ('Digche replacements'), and the source scope ('an icon from Lucide, Heroicons, Material Symbols, Font Awesome, or another library'). It is distinct from a generic icon search, though it does not explicitly contrast with the sibling recommend_icons tool.

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 description gives a practical usage directive: 'Include the UI context for a more useful match' and notes the context may be English or Persian. However, it does not explain when to choose this tool over search_icons or recommend_icons, nor when it should not be used.

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

All Digche Icons tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?