Skip to main content
Glama
gxxHuang
by gxxHuang

add_custom_url_library

Add a custom URL library to iKuai routers with a name and list of domains for implementing custom URL filtering and access control.

Instructions

添加自定义网址库

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
commentNo
domainsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'add custom URL library' with no details about side effects, idempotency, required permissions, error behavior, or what happens on duplicate libraries. This is a significant gap for a mutation tool.

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

Conciseness2/5

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

The description is extremely short, but it is under-specified rather than concise. It consists of a single phrase that adds no value beyond the tool name. It is not appropriately sized for a meaningful tool description.

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 the tool has 3 parameters, no annotations, and no schema descriptions, the description is grossly incomplete. It does not explain return values, expected input formats, or how this tool fits into the broader workflow. The output schema exists but the description does not leverage it.

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 mentions none of the parameters (name, comment, domains). The agent cannot infer what these fields mean, their formats, or how they relate to each other from the description alone. The description fails to compensate for the lack of schema descriptions.

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

Purpose2/5

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

The description '添加自定义网址库' is a direct translation/restatement of the tool name 'add_custom_url_library'. It repeats the name without adding any specific detail about the resource or action beyond what the name already communicates. There is no distinction from sibling tools like 'add_url_blacklist' or 'add_domain_blacklist'.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or exclusions. The agent is left without any information about when this tool should be preferred over similar tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gxxHuang/ikuai-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server