Skip to main content
Glama

Digche Icons

by io.github.Elinaseri
OverviewDiscussionsAdmin

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

NameRequiredDescriptionDefault
limitNo1 to 20. Out-of-range values are clamped.
queryYesFunctional intent in English or Persian, such as previous page, analytics, delete item, or «سبد خرید».
styleNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / style / enum
      Previous value: -[
-  "Bold",
-  "Bulk",
-  "Linear",
-  "Outline",
-  "Animated"
-]New value: +[
+  "Bold",
+  "Bulk",
+  "Linear",
+  "Outline",
+  "Animated",
+  "Primary",
+  "Monochrome",
+  "Light",
+  "Dark"
+]
  2. Changed1 schema field changed
    • 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 «سبد خرید»."
  3. Changed6 schema fields changed
    • 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"
  4. First observed

TDQS

A3.7/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 and does disclose useful behavior: bilingual English/Persian matching against stored Persian aliases, and a return of a paste-ready summary plus a preview image. It omits pagination/result-set behavior and any rate or scope limits, but as a read-only search those gaps are minor.

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?

Four sentences, front-loaded with what is searched, then the Persian-language tip, then the when-to-use cue, then the return shape. No sentence restates structured data or could be cut without losing information.

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?

No output schema exists, and the description does step up by describing the return value. But for a 4-parameter tool with half its schema undocumented, leaving style and category entirely unexplained means an agent gets no guidance on when to narrow by style or category slug.

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 coverage is 50%: query and limit are documented in the schema, while style (enum) and category (pattern) have no descriptions anywhere. The description reinforces that query is a functional intent rather than a literal name match, but adds nothing about style or category, so it does not compensate for the coverage gap.

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?

States a specific verb and resource (search published Digche icons) plus the searchable dimensions: name, alias, use case, tag, category, functional meaning. It does not name any sibling, so an agent must still infer how this differs from recommend_icons or preview_icons.

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?

"Use this before choosing a UI icon" gives a clear ordered context, and the Persian-wording tip is a concrete usage instruction. However, no alternative is named and no when-not condition is stated, even though recommend_icons and preview_icons look like overlapping siblings.

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

All Digche Icons toolsInspect
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