Skip to main content
Glama
Sign In
material-icons-agent-skill

material-icons-agent-skill

by ByteFlipper-58
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_icons

Search official Google Material Symbols by keyword and style. Filter results by outlined, rounded, or sharp variants and set the number of icons returned.

Instructions

Search official Material Symbols by meaning and style.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_icons"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
styleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the search intent and does not mention what the function returns, whether it is read-only, any rate limits, or how results are ordered. This is a significant transparency gap for a tool with no other metadata.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no extraneous words. However, its brevity contributes to the lack of detail in other dimensions, so while it is concise, it is not fully helpful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema or annotations, the description should explain the return value and behavior, but it does not. It fails to mention whether results are icon names, identifiers, or metadata, and does not describe the effect of the limit parameter, making the tool under-specified for an agent to fully understand its behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, so the description must compensate for all parameters. It maps 'meaning' to the query parameter and 'style' to the style parameter, but it omits the limit parameter entirely and doesn't clarify what 'meaning' entails (e.g., search by name or tags). This partial coverage leaves the parameter semantics incomplete.

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 uses the specific verb 'Search' and identifies the resource as 'official Material Symbols', with scope 'by meaning and style'. This clearly distinguishes it from sibling tools like delete_icon, import_icon, and update_icon, which are mutation operations.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to choose this tool over alternatives. It does not mention any exclusions or compare to sibling tools such as audit_icons or preview_icons, leaving the usage context implied rather than stated.

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