Skip to main content
Glama
yingcaihuang

Racore Cloud CDN MCP Server

by yingcaihuang

set_domain_referer_blackwhitelist

Control access to your CDN domain by configuring a Referer blacklist or whitelist to block or allow traffic based on referrer URLs.

Instructions

设置域名 Referer 黑白名单

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes名单类型:off=关闭,black=黑名单,white=白名单
valueNoReferer 列表 JSON 数组,如 ["example.com","*.test.com"]
domainYes域名
allow_emptyNo允许空 Referer:on=允许,off=不允许
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 only states that the tool sets a black/white list but does not reveal whether it overwrites existing settings, the effect on ongoing operations, or any side effects. This is insufficient 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.

Conciseness4/5

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

The description is a single concise sentence with no unnecessary words. However, it could be slightly expanded to include key details without becoming verbose.

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 the tool has 4 parameters and no output schema, the description is too brief. It does not explain the overall purpose of Referer filtering, how the parameters interact, or what the tool does beyond setting the list. More context is needed for an agent to use it correctly.

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

Parameters3/5

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

Schema coverage is 100%, with all parameters described in the input schema. The description adds no additional meaning beyond what is already in the schema, so the baseline score of 3 is appropriate.

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 'Set domain Referer black/white list' clearly states the verb (set) and resource (domain Referer list), making the tool's purpose understandable. However, it does not differentiate from sibling tools like set_domain_ip_blackwhitelist or set_domain_ua_blackwhitelist, which have identical phrasing.

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 vs. alternatives such as set_domain_ip_blackwhitelist or query_domain_referer_blackwhitelist. The description does not mention prerequisites, use cases, or exclusions, leaving the agent to 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.

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/yingcaihuang/racorecloud-mcp'

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