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

material-icons-agent-skill

by ByteFlipper-58
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

validate_icon_usage

Identify icons missing accessibility labels to ensure proper screen reader support. Validates Material Symbols usage and reports likely missing labels.

Instructions

Report likely missing accessibility labels for icon usage.

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": {
      "root": "<root>"
    },
    "name": "validate_icon_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootYes

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 of behavioral disclosure. It implies a read-only report and uses 'likely' to suggest heuristic analysis, but does not disclose permissions, scope, or whether any changes are made. No side effects or limitations are mentioned.

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 redundant words. While concise, it may be under-specified, but it earns high marks for efficiency and directness.

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?

Given there is no output schema, no annotations, and only one parameter with no description, the tool description does not explain what the report contains, how 'likely missing' is determined, or what inputs are expected. It is minimally adequate but leaves clear gaps.

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 coverage is 0% and the description makes no mention of the 'root' parameter. The parameter name is ambiguous (e.g., root directory, root element) and the description does not compensate for the lack of schema documentation.

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 uses a specific verb ('Report') and resource ('icon usage') to indicate it finds likely missing accessibility labels, which is distinct from sibling tools like 'audit_icons' that may perform broader audits. However, it does not elaborate on the scope or type of icons, so it is clear but not fully differentiated.

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 given for when to use this tool versus alternatives like 'audit_icons' or 'search_icons'. The description does not mention context, prerequisites, or exclude cases, leaving the agent without usage direction.

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