Skip to main content
Glama
BACH-AI-Tools

Thesaurus By Api Ninjas

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Thesaurus By Api Ninjas MCP Server

English | 简体中文 | 繁體中文

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

🚀 使用 EMCP 平台快速体验

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

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

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

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

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

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

EMCP 平台优势：

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

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

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

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

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

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

Related MCP server: Dictionary By Api Ninjas

简介

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

  • PyPI 包名: bach-thesaurus_by_api_ninjas

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-thesaurus_by_api_ninjas

从源码安装:

pip install -e .

运行

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

# 运行（uvx 会自动安装并运行）
uvx --from bach-thesaurus_by_api_ninjas bach_thesaurus_by_api_ninjas

# 或指定版本
uvx --from bach-thesaurus_by_api_ninjas@latest bach_thesaurus_by_api_ninjas

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

python server.py

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

# 安装
pip install bach-thesaurus_by_api_ninjas

# 运行（命令名使用下划线）
bach_thesaurus_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-thesaurus_by_api_ninjas": {
      "command": "uvx",
      "args": ["--from", "bach-thesaurus_by_api_ninjas", "bach_thesaurus_by_api_ninjas"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

在 Claude Desktop 中使用

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

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

可用工具

此服务器提供以下工具:

v1thesaurus

API Ninjas Thesaurus API endpoint. Returns a list of synonyms and a list of antonyms for a given word.

端点: GET /v1/thesaurus

参数:

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

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

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

版本: 1.0.0

Available Tools

1 tool
v1thesaurusB

API Ninjas Thesaurus API endpoint. Returns a list of synonyms and a list of antonyms for a given word.

ParametersJSON Schema
NameRequiredDescriptionDefault
wordYesword to look up.

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the return value (lists of synonyms and antonyms) but doesn't mention any behavioral traits such as rate limits, authentication requirements, error handling, or whether it's a read-only operation. The description is functional but lacks important operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is extremely concise and front-loaded, consisting of a single sentence that directly states the tool's function. There is no wasted language, and it efficiently communicates the core purpose without unnecessary 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 tool's low complexity (single parameter, no annotations, no output schema), the description is minimally adequate. It explains what the tool returns but doesn't cover behavioral aspects like error cases or performance. Without an output schema, it could benefit from more detail on return format, but it meets basic requirements for a simple lookup tool.

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?

The input schema has 100% description coverage, with the single parameter 'word' documented as 'word to look up.' The description adds no additional meaning beyond this, as it only reiterates that it takes 'a given word.' Since the schema does the heavy lifting, 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 clearly states the tool's purpose: 'Returns a list of synonyms and a list of antonyms for a given word.' It specifies the verb ('Returns'), resource ('list of synonyms and antonyms'), and target ('given word'). However, since there are no sibling tools, it doesn't need to differentiate from alternatives, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. It states what the tool does but offers no context about when it's appropriate, what prerequisites might be needed, or any limitations. Without sibling tools, explicit alternatives aren't required, but general usage context is missing.

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 update
    • First observedv1thesaurus
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.3/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as returning synonyms and antonyms for a given word, making it distinct by default.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'v1thesaurus' follows a single pattern without any deviations or mixing of conventions.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and scope. While it might suffice for a simple thesaurus lookup, it feels thin and lacks depth for broader language processing tasks.

Completeness3/5

The tool covers the basic lookup of synonyms and antonyms, which is the core function of a thesaurus. However, there are notable gaps such as no support for related words, word definitions, examples, or advanced language features, making the surface incomplete for comprehensive language analysis.

Maintenance

ActivityInactive
ResponsivenessNo issues

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/thesaurus_by_api_ninjas'

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