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

material-icons-agent-skill

by ByteFlipper-58
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_icon

Re-download and replace an existing local Material Symbol to update it. Provide the icon name, target platform, and root path, then confirm to overwrite the current file.

Instructions

Explicitly re-download and replace an already imported local icon.

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": {
      "name": "<name>",
      "target": "<target>",
      "root": "<root>",
      "confirm": "<confirm>"
    },
    "name": "update_icon"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
rootYes
styleNo
targetYes
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It mentions 'replace' but does not disclose that the operation overwrites an existing local file, requires network access, or that the 'confirm' parameter is a safety gate. This leaves the destructive nature implicit rather than explicit.

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 a single sentence with no wasted words. It is front-loaded and concise, earning a high score for conciseness even though it lacks detail.

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

Completeness1/5

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

Given five parameters, no output schema, and no annotations, the description is severely under-specified. It fails to cover parameter meanings, usage context, side effects, or network requirements, making it inadequate for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain any of the five parameters (name, root, style, target, confirm). The agent must rely solely on field names and enums, so the description adds no value beyond the schema.

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 states the action ('re-download and replace') and the resource ('an already imported local icon'), distinguishing it from import_icon (new icons) and delete_icon (removal). It lacks explicit sibling differentiation but the intent is unambiguous.

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?

No guidance is provided on when to use this tool instead of alternatives like delete_icon + import_icon, or the context for refreshing an icon. The word 'already imported' implies a precondition but there is no explicit when-to-use guidance.

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