Digche Icons

Search Digche icons

search_icons

Search published Digche icons by name, alias, use case, tag, category, or functional meaning. Queries work in English or Persian - every icon carries Persian aliases, so pass the user's own Persian wording instead of translating it first. Use this before choosing a UI icon. Returns a paste-ready summary and a preview image of the results.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	1 to 20. Out-of-range values are clamped.
`query`	Yes	Functional intent in English or Persian, such as previous page, analytics, delete item, or «سبد خرید».
`style`	No
`category`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 19, 2026

changedInput schema / properties / query / description

Previous value: -"Functional intent such as previous page, analytics, or delete item."New value: +"Functional intent in English or Persian, such as previous page, analytics, delete item, or «سبد خرید»."

Changed6 schema fields changedAug 17, 2026
- addedInput schema / properties / limit / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]
```
- removedInput schema / properties / limit / default
```
Removed value: -8
```
- addedInput schema / properties / limit / description
```
Added value: +"1 to 20. Out-of-range values are clamped."
```
- removedInput schema / properties / limit / maximum
```
Removed value: -20
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- removedInput schema / properties / limit / type
```
Removed value: -"integer"
```
First observedAug 11, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses how queries behave (bilingual, Persian aliases) and what is returned (paste-ready summary and preview image). While it doesn't explicitly state 'read-only,' the word 'Search' and the output description strongly imply a non-destructive query operation.

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 three tight sentences with no fluff: purpose, usage guidance, and return summary. Every sentence contributes actionable information, and the most important facts are front-loaded.

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 simple 4-parameter search tool with no output schema, the description covers the essential call path: what to search, how to phrase the query, and what to expect in the response. Minor gaps remain around limit/style/category usage, but these are partially self-documenting in the schema and the tool is simple enough that the description is nearly sufficient.

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 description adds useful meaning to the query parameter by listing matching fields and language handling. However, it doesn't explain the limit clamp, the style enum values, or the category slug pattern, and with 50% schema coverage the added value only partially compensates for the undocumented parameters.

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 clearly identifies the action ('Search published Digche icons') and enumerates search dimensions (name, alias, use case, tag, category, functional meaning). It positions the tool as the entry point for icon selection with 'Use this before choosing a UI icon,' though it doesn't explicitly name sibling tools or say what it is not.

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 explicit timing guidance: use this before choosing a UI icon. It also provides an actionable language rule—pass the user's own Persian wording instead of translating it first. It doesn't discuss when to prefer a sibling tool, but the context is clear for the common case.

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?