Skip to main content
Glama
if530770

redfox-mcp-server

by if530770

multi-wordcheck

Detect prohibited and sensitive words in copywriting across Xiaohongshu, Douyin, WeChat, Bilibili, and Kuaishou. Submit content and platform to receive a compliance check result.

Instructions

多平台违禁词检测,检查文案中的敏感词并返回检测结果

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes待检测文案内容
platformNo目标平台xiaohongshu

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.4

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description bears the full burden. It only says 'returns detection results' without clarifying the output format, whether it blocks on sensitive words, or how multi-platform results are aggregated. This is a thin disclosure for an unannotated 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 efficient sentence that front-loads the core purpose. There is no wasted wording, though it is arguably too sparse to cover behavioral details.

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?

Given the simplicity of the two-parameter schema, the description is minimally adequate, but with no output schema and no annotation, the vague 'returns detection results' leaves the agent unsure of what the response looks like. More detail about multi-platform result structure would improve completeness.

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 description coverage is 100%, with both 'content' and 'platform' clearly described in the input schema. The description adds no new parameter-level meaning beyond what the schema already provides, so the baseline 3 applies.

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 states a specific verb (detect) and resource (prohibited/sensitive words in copy), and the 'multi-platform' qualifier differentiates it from single-platform siblings like xiaohongshu-prohibited-word, douyin-prohibited-word, and wechat-prohibited-word. However, it does not list which platforms are covered, so it stops short of being fully precise.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'multi-platform' implies this tool is for checking across multiple platforms, but the description gives no explicit when-to-use guidance, no exclusions, and no mention of alternatives. Usage context is inferable but not stated.

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/if530770/redfox-mcp'

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