Skip to main content
Glama
gxxHuang
by gxxHuang

List Url Blacklist

list_url_blacklist
Read-only

Retrieve URL blacklist and whitelist entries from an iKuai router to review blocked and permitted web addresses.

Instructions

列出网址黑白名单(tab: 网址黑白名单)

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered, but the description adds nothing behavioral beyond that — no indication of scope, size, pagination, or whether the result mixes black and white lists. The parenthetical tab label is navigational, not behavioral.

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?

Very short and front-loaded with no filler, though the parenthetical tab label is largely redundant with the name itself. Nothing extraneous, but also very little substance.

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?

For a zero-param read tool with an output schema and readOnlyHint, the description is minimally sufficient, but it leaves an important ambiguity: whether "网址黑白名单" returns blacklist entries, whitelist entries, or both, which matters in a family of separate blacklist/whitelist tools.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to document; the baseline for a 0-param tool applies. No parameter claims are made or needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"列出网址黑白名单" states a verb and resource, but largely restates the tool name; the parenthetical tab hint (网址黑白名单) adds minor UI context. Against siblings like list_domain_blacklist, list_url_redirects, and list_wireless_blackwhite_list, it does not clarify whether this returns blacklist, whitelist, or both.

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 on when to use this versus list_domain_blacklist, list_url_keywords, or list_url_redirects, and no prerequisites or exclusions mentioned. The agent must infer usage from the name alone.

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