Skip to main content
Glama
BACH-AI-Tools

Dictionary By Api Ninjas

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Dictionary By Api Ninjas MCP Server

English | 简体中文 | 繁體中文

用于访问 Dictionary By Api Ninjas API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

  3. 🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器

  4. 🔍 搜索或找到本服务器（bach-dictionary_by_api_ninjas）

  5. 🎉 点击 "安装 MCP" 按钮

  6. ✅ 完成！即可在您的应用中使用

EMCP 平台优势：

  • ✨ 零配置：无需手动编辑配置文件

  • 🎨 可视化管理：图形界面轻松管理所有 MCP 服务器

  • 🔐 安全可靠：统一管理 API 密钥和认证信息

  • 🚀 一键安装：MCP 广场提供丰富的服务器选择

  • 📊 使用统计：实时查看服务调用情况

立即访问 EMCP 平台 开始您的 MCP 之旅！

Related MCP server: Cambridge Dictionary MCP Server

简介

这是一个 MCP 服务器，用于访问 Dictionary By Api Ninjas API。

  • PyPI 包名: bach-dictionary_by_api_ninjas

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-dictionary_by_api_ninjas

从源码安装:

pip install -e .

运行

方式 1: 使用 uvx（推荐，无需安装）

# 运行（uvx 会自动安装并运行）
uvx --from bach-dictionary_by_api_ninjas bach_dictionary_by_api_ninjas

# 或指定版本
uvx --from bach-dictionary_by_api_ninjas@latest bach_dictionary_by_api_ninjas

方式 2: 直接运行（开发模式）

python server.py

方式 3: 安装后作为命令运行

# 安装
pip install bach-dictionary_by_api_ninjas

# 运行（命令名使用下划线）
bach_dictionary_by_api_ninjas

配置

API 认证

此 API 需要认证。请设置环境变量:

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bach-dictionary_by_api_ninjas": {
      "command": "uvx",
      "args": ["--from", "bach-dictionary_by_api_ninjas", "bach_dictionary_by_api_ninjas"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

在 Claude Desktop 中使用

编辑 Claude Desktop 配置文件 claude_desktop_config.json:

{
  "mcpServers": {
    "bach-dictionary_by_api_ninjas": {
      "command": "uvx",
      "args": ["--from", "bach-dictionary_by_api_ninjas", "bach_dictionary_by_api_ninjas"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

可用工具

此服务器提供以下工具:

v1dictionary

API Ninjas Dictionary API endpoint.

端点: GET /v1/dictionary

参数:

  • word (string) 必需: Word to look up.

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

此服务器由 API-to-MCP 工具生成。

版本: 1.0.0

Available Tools

1 tool
v1dictionaryC

API Ninjas Dictionary API endpoint.

ParametersJSON Schema
NameRequiredDescriptionDefault
wordYesWord to look up.

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it's a dictionary API endpoint. It fails to disclose behavioral aspects like what happens on missing words, authentication needs, or rate limits.

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 a single sentence but is under-specified. It does not provide enough information to be useful, failing to earn its place by adding value beyond the tool name.

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 only one parameter and no output schema or annotations, the description should compensate but fails to provide context about return values, error handling, or usage notes.

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% (the 'word' parameter already has a description 'Word to look up.'). The tool description adds no additional meaning beyond this, so baseline 3 is appropriate.

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 'API Ninjas Dictionary API endpoint' is a tautology of the tool name 'v1dictionary' and does not specify the action (e.g., look up word, get definition). It lacks specificity about what the tool actually does.

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 or any alternatives. There are no siblings, but the description does not clarify the usage context or prerequisites.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedv1dictionary
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3/5.0
Disambiguation5/5

Only one tool exists, so there is no ambiguity in tool selection. The single tool has a clearly distinct purpose as a dictionary lookup endpoint.

Naming Consistency5/5

With only one tool, naming is inherently consistent. The name 'v1dictionary' follows a reasonable pattern of version prefix and resource name.

Tool Count5/5

A single dictionary lookup tool is appropriate for the server's intended scope. Many dictionary APIs expose only one endpoint, so the count is well-scoped.

Completeness4/5

The single tool likely covers basic dictionary lookups, but may lack additional features like synonyms or examples. However, for a minimal dictionary service, it is reasonably complete.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

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/BACH-AI-Tools/dictionary_by_api_ninjas'

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