query_domain_referer_blackwhitelist
Retrieve the configured referer blacklist or whitelist for a specific CDN domain to verify access control settings.
Instructions
查询域名 Referer 黑白名单
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | 域名 |
Retrieve the configured referer blacklist or whitelist for a specific CDN domain to verify access control settings.
查询域名 Referer 黑白名单
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | 域名 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not disclose any behavioral traits beyond the name. Since no annotations are present, the description carries the full burden, and it fails to mention that the tool is read-only, requires no special permissions, or any other behavioral details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short and to the point, with no unnecessary words. It is appropriately sized for the tool's simplicity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
While the tool is simple, the description could provide more context about the black/whitelist content (e.g., what fields are returned). Without an output schema, the description should compensate but does not.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a single parameter 'domain' described as '域名'. The description adds no additional meaning beyond what the schema already provides, hitting the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description '查询域名 Referer 黑白名单' clearly states the action (query) and the resource (domain Referer black/whitelist). It distinguishes from sibling tools like 'set_domain_referer_blackwhitelist' and other query tools for different settings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidelines are provided. The tool is straightforward as a query, but there is no mention of when to use it versus other query tools or any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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