Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Random Word By Api Ninjas give me a random adjective for my poem"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
用于访问 Random Word By Api Ninjas API 的 MCP 服务器。
EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器（bach-random_word_by_api_ninjas）
🎉 点击 "安装 MCP" 按钮
✅ 完成！即可在您的应用中使用
✨ 零配置：无需手动编辑配置文件
🎨 可视化管理：图形界面轻松管理所有 MCP 服务器
🔐 安全可靠：统一管理 API 密钥和认证信息
🚀 一键安装：MCP 广场提供丰富的服务器选择
📊 使用统计：实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅！
Related MCP server: Thesaurus By Api Ninjas
这是一个 MCP 服务器，用于访问 Random Word By Api Ninjas API。
PyPI 包名: bach-random_word_by_api_ninjas
版本: 1.0.0
传输协议: stdio
pip install bach-random_word_by_api_ninjaspip install -e .# 运行（uvx 会自动安装并运行）
uvx --from bach-random_word_by_api_ninjas bach_random_word_by_api_ninjas
# 或指定版本
uvx --from bach-random_word_by_api_ninjas@latest bach_random_word_by_api_ninjaspython server.py# 安装
pip install bach-random_word_by_api_ninjas
# 运行（命令名使用下划线）
bach_random_word_by_api_ninjas此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:
{
"mcpServers": {
"bach-random_word_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-random_word_by_api_ninjas", "bach_random_word_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"bach-random_word_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-random_word_by_api_ninjas", "bach_random_word_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}此服务器提供以下工具:
v1randomwordAPI Ninjas Random Word API endpoint. Returns a random word.
端点: GET /v1/randomword
参数:
type (string): Type of word. Possible values are: noun, verb, adjective, adverb.
传输协议: stdio
HTTP 客户端: httpx
MIT License - 详见 LICENSE 文件。
此服务器由 API-to-MCP 工具生成。
版本: 1.0.0
API Ninjas Random Word API endpoint. Returns a random word.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Type of word. Possible values are: noun, verb, adjective, adverb. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states the tool returns a random word but does not disclose behavioral traits such as rate limits, authentication needs, error handling, or response format. This leaves significant gaps in understanding how the tool behaves in practice.
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 extremely concise and front-loaded, consisting of only two sentences that directly state the tool's purpose and source. Every sentence earns its place with zero waste, making it efficient and well-structured.
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?
Given the lack of annotations and output schema, the description is incomplete. It does not explain return values, error conditions, or other contextual details needed for effective use. While the tool is simple, the description fails to provide sufficient completeness for a tool with no structured support.
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?
The input schema has 100% description coverage, documenting the optional 'type' parameter with possible values. The description does not add any parameter semantics beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without compensating value.
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 clearly states the tool's purpose: 'Returns a random word' with the specific source 'API Ninjas Random Word API endpoint.' It uses a specific verb ('Returns') and resource ('random word'), but since there are no sibling tools, it cannot differentiate from them, which prevents a perfect score.
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?
The description provides no guidance on when to use this tool versus alternatives. It mentions the API endpoint but does not specify use cases, prerequisites, or exclusions. Without sibling tools, there is no explicit comparison, but general usage context is still missing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1randomwordWith only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as returning a random word, making it impossible to confuse with other tools.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'v1randomword' follows a single pattern with no deviations to compare against.
A single tool is too few for most practical server purposes, as it limits functionality and scope. While it matches the simple API of returning a random word, it feels thin and underdeveloped for broader agent use.
For the narrow domain of fetching a random word, the tool surface is complete. There are no gaps since the only required operation is provided, and no additional actions like filtering or updating are needed for this purpose.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
API Ninjas MCP — wraps the multi-endpoint API Ninjas data API (api-ninjas.com)
Words MCP — wraps Datamuse API (free, no auth required)
Dictionary MCP — wraps Free Dictionary API (free, no auth)
Get a random dad joke or search by keyword to fit any moment. Retrieve specific jokes by ID for re…
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/random_word_by_api_ninjas'
If you have feedback or need assistance with the MCP directory API, please join our Discord server