en es ja ko zh

ToolBox MCP Server

Name: ToolBox MCP Server
Author: xiaoguomeiyitian

by xiaoguomeiyitian

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

ToolBox MCP 服务器

GitHub 发布

一个由人工智能驱动的自动化工具开发平台，提供：

🧩 模块化架构 - 通过src/tools目录进行工具热加载🤖 AI 辅助 - 用于自然语言到工具模板转换的 AI 引擎🚀 企业级功能 - 集成生产环境服务，例如 MongoDB/Redis/SSH🔄 实时更新 - 通过buildReload_tool实现零停机部署

graph LR
    A[Developer] -->|Create| B(Tool Template)
    B --> C{AI Verification}
    C -->|Pass| D[Automatic Loading]
    C -->|Fail| E[Human Review]
    D --> F[API Exposure]
    F --> G[Client Invocation]
    style C fill:#4CAF50,stroke:#333

中文詳細

贡献

贡献指南（英文）贡献指南（中文）

工具规格

Related MCP server: Jachy MCP Server

特征

工具

查看完整的工具规格和详细文档： TOOL.md

资源

资源是工具执行后动态生成的。例如， create_note工具会创建一个可通过其 URI 访问的笔记资源。

工作流工具

workflow_tool是一个功能强大的工具，可以通过将多个工具链接在一起来编排复杂的工作流。它支持：

**串行和并行执行：**以顺序或并行的方式执行工具。
**事务管理：**使用错误处理补偿机制来管理事务。
**详细报告：**生成有关工作流执行的详细报告，包括每个步骤的状态、执行时间和结果。
**可定制的输出：**指定输出文件来保存工作流执行报告。

提示

summarize_notes ：生成使用create_note工具创建的注释的摘要。

开发指南

添加新工具

graph TD
    A[Create Tool Template] --> B{AI Automatic Verification}
    B -->|Schema Validation| C[Generate Test Cases]
    B -->|Risk Exists| D[Human Review]
    C --> E[Unit Testing]
    D -->|Approve| E
    E --> F[Security Scanning]
    F --> G[Build Integration]
    G --> H[Version Release]
    style A fill:#f9f,stroke:#333
    style H fill:#4CAF50,stroke:#333

详细开发流程

模板创建：在src/tools/目录中创建一个新的工具文件
AI验证：自动检查参数Schema合规性
测试生成：根据功能描述生成测试用例
安全审查：静态代码分析和依赖性检查
持续集成：通过 GitHub Actions 实现自动部署

查看完整开发指南： prompt.md参考现有实现：工具示例

发展

安装依赖项：

npm install

构建服务器：

npm run build

对于使用自动重建的开发：

npm run watch

市场提交

工具箱徽标 适用于 Claude Desktop 的无缝集成自动化工具包

安装

要与 Claude Desktop 应用程序集成，请将以下服务器配置添加到：

macOS： ~/Library/Application Support/Claude/claude_desktop_config.json
Windows： %APPDATA%/Claude/claude_desktop_config.json

// Cline MCP server configuration file
{
  "command": "node",
  "args": [
    "--inspect=9229",
    "/MCP/ToolBox/build/index.js"
  ],
  "env": {
    "MONGO_URI": "mongodb://user:password@host:port/db",
    "MONGO_INDEX_OPS": "true",
    "REDIS_URI": "redis://:password@host:port",
    "SSH_server1_URI": "username:password@host:port",
    "GEMINI_API_KEY":"GEMINI_API_KEY",
    "SSEPORT": "8080" // Optional: If set, the server will use SSE transport on this port. Otherwise, it defaults to Stdio transport.
  },
  "disabled": false,
  "autoApprove": []
}

核心价值观

🚀企业级自动化利用 package.json 配置，提供：

全局 CLI 工具安装（ tbx命令）
工作流调度引擎
多平台支持（Windows/macOS）
混合云部署能力（MongoDB/Redis/SSH）

🔧开发者友好

强类型 TypeScript 实现
实时调试支持（--inspect 标志）
VSCode 调试配置模板

热重载机制：

graph LR
  A[Code Modification] --> B[buildReload_tool]
  B --> C[Automatic Compilation]
  C --> D[Security Verification]
  D --> E[Tool Reloading]
  style B fill:#4CAF50,stroke:#333

通过调用buildReload_tool实现：

零停机更新
自动依赖树解析
版本兼容性检查
沙盒环境测试

调试

由于 MCP 服务器使用 stdio 通信，调试起来可能比较困难。以下是一些方法：

🚧 免责声明

敏感数据

请勿在容器中配置敏感数据。这些数据包括 API 密钥、数据库密码等。

除非 LLM 在您的本地机器上运行，否则与 LLM 交换的任何敏感数据本质上都会受到损害。

法律责任⚠️

⚠️ 该工具根据 MIT 许可证“按原样”提供，不提供任何担保
⚠️ 开发者不对直接/间接损害负责
⚠️ 用户自行承担因容器配置不当而产生的所有风险
⚠️ 严禁任何非法或破坏性使用
⚠️ 请参阅许可证以了解完整条款

**Node.js 检查器：**使用--inspect=9229标志启动服务器：

node --inspect=9229 build/index.js

然后，通过导航到chrome://inspect使用 Chrome DevTools 连接到服务器。

**MCP 检查器：**利用MCP 检查器，这是一个可通过inspector npm 脚本访问的专用调试工具：
VSCode 调试

要使用 VSCode 进行调试，请创建具有以下配置的.vscode/launch.json文件：

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "attach",
            "name": "ToolBox",
            "address": "localhost",
            "port": 9229,
            "localRoot": "${workspaceFolder}"
        }
    ]
}

然后，使用--inspect=9229标志启动服务器并附加 VSCode 调试器。

Available Tools

17 tools

buildReload_toolD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

calculator_toolD

ParametersJSON Schema

Name	Required	Description
`calculation_type`	Yes	The type of calculation to perform.
`expression`	No	The mathematical expression to evaluate (for 'evaluate_expression').
`statistics_operation`	No
`data_points`	No
`data_set_x`	No
`data_set_y`	No
`geometry_operation`	No
`radius`	No
`length`	No
`width`	No
`side`	No
`financial_math_operation`	No
`principal`	No
`rate`	No	Interest rate as a percentage (e.g., 5 for 5%).
`time`	No	Time in years.
`n_compounding_periods`	No
`future_value`	No
`logic_operation`	No
`operand_a`	No
`operand_b`	No
`number_theory_operation`	No
`number_a`	No
`number_b`	No
`number_theory_modulus`	No
`combinatorics_operation`	No
`n_value`	No
`r_value`	No
`probability_operation`	No
`probability_a`	No
`probability_b`	No
`probability_a_given_b`	No
`probability_b_given_a`	No
`set_theory_operation`	No
`set_a`	No
`set_b`	No
`complex_number_operation`	No
`complex_a`	No	First complex number (e.g., '3 + 4i').
`complex_b`	No	Second complex number (e.g., '1 - 2i').
`precision_level`	No

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

cli_toolD

ParametersJSON Schema

Name	Required	Description	Default
`command`	No	要执行的单行命令
`commands`	No	要执行的多行命令序列 (与 'command' 互斥)
`mode`	No	执行模式: sync (同步阻塞), async (异步非阻塞)	sync
`timeout`	No	命令执行的超时时间（秒）
`cwd`	No	命令执行的工作目录 (绝对路径)
`platform`	No	强制指定执行命令的操作系统环境	auto
`safe_mode`	No	是否启用危险命令过滤

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

compress_toolD

ParametersJSON Schema

Name	Required	Description
`action`	Yes	Action type: compress or extract
`sourcePath`	Yes	Absolute path to source file/directory
`destinationPath`	Yes	Absolute path to destination file/directory
`format`	Yes	Compression format: zip, tar, tar.gz

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

create_noteD

ParametersJSON Schema

Name	Required	Description	Default
`title`	Yes	Note title
`content`	Yes	Note content

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

excel_toolD

ParametersJSON Schema

Name	Required	Description
`action`	Yes	Action to perform: read, write, or convert_json_to_xlsx
`filePath`	Yes	Absolute path to the input file
`outputFilePath`	No	Absolute path to the output file (required for write and convert actions)
`format`	Yes	File format: xlsx, csv
`data`	No	Data to write (required for write action)
`options`	No	Additional options

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

fileSystem_toolD

ParametersJSON Schema

Name	Required	Description
`operation`	Yes	要执行的文件系统操作 (例如: read, write, copy)
`sourcePath`	Yes	源文件的绝对路径
`targetPath`	No	目标文件的绝对路径 (用于 copy/move 操作)
`content`	No	要写入文件的内容 (用于 'write' 操作)
`recursive`	No	递归地对目录应用操作
`overwrite`	No	在 copy/move 操作中覆盖已存在的文件
`showHidden`	No	在 list/listDetails 中包含隐藏文件/目录
`fileMode`	No	文件模式（权限），使用八进制格式 (例如, 755)
`uid`	No	用于 chown 操作的用户 ID
`gid`	No	用于 chown 操作的组 ID

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

gemini_image_toolD

ParametersJSON Schema

Name	Required	Description	Default
`operation`	Yes	generate_image: Generate new image, edit_image: Edit existing image
`prompt`	Yes	Prompt for image generation/editing
`inputImage`	No	Image path (required for edit_image)
`outputDir`	Yes	Output directory path
`fileName`	No	Output file name template	image-${year}_${month}_${day}_${hour}_${minute}_${second}.png
`temperature`	No	Temperature of the model
`topP`	No	Top P of the model
`topK`	No	Top K of the model
`maxOutputTokens`	No	Maximum number of output tokens

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

image_toolD

ParametersJSON Schema

Name	Required	Description
`sourcePath`	Yes	Source file or directory path
`outputPath`	No	Output directory path. Defaults to a new file (e.g., 'source.processed.jpg') or a new directory (e.g., 'source_processed').
`quality`	No	Compression quality for JPEG/WebP/AVIF/TIFF (1-100, defaults to 80)
`compressionLevel`	No	PNG compression level (0-9, defaults to 6)
`resize`	No	Resize options
`format`	No	Output format (optional, keeps original if not specified)
`recursive`	No	Process subdirectories recursively
`backupDir`	No	Backup directory path (optional)

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

log_toolD

ParametersJSON Schema

Name	Required	Description
`pageSize`	No	Logs per page (1-100)
`page`	No	Page number (>= 1)
`toolName`	No	Regex to match tool name
`status`	No	Log status (success or error)
`minDuration`	No	Minimum duration (ms)
`maxDuration`	No	Maximum duration (ms)
`startTime`	No	Start time (ISO8601)
`endTime`	No	End time (ISO8601)

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

mongo_toolD

ParametersJSON Schema

Name	Required	Description
`dbName`	Yes	MongoDB 数据库名称
`collectionName`	No	MongoDB 集合名称
`queryType`	No	MongoDB 查询类型
`operationType`	No	数据库管理操作类型 (索引/集合管理)
`where`	No	查询条件 (BSON/JSON 对象)
`data`	No	用于插入或替换的数据 (单个对象或对象数组)
`updateOperators`	No	更新操作符 (例如: { $set: { field: 'value' } })
`pipeline`	No	聚合管道阶段 (对象数组)
`field`	No	用于 distinct 操作的字段名
`indexes`	No	索引规范 (例如: { field: 1 })
`newName`	No	用于 renameCollection 的新名称
`bulkOperations`	No	批量写入操作数组
`options`	No	其他选项 (例如: { sort: { field: -1 }, limit: 10 })

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

redis_toolD

ParametersJSON Schema

Name	Required	Description	Default
`command`	Yes	要执行的 Redis 命令 (例如, 'GET', 'SET')
`args`	No	命令的参数列表 (例如: ["mykey", "myvalue"])

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

schedule_toolD

ParametersJSON Schema

Name	Required	Description
`action`	Yes	Action type (create/cancel/list)
`time`	No	Absolute execution time (YYYY-MM-DD HH:mm:ss)
`delaySeconds`	No	Delay execution by N seconds
`interval`	No	Recurring interval pattern (e.g. 'every@5m')
`toolName`	No	Tool to execute (e.g. 'time_tool')
`toolArgs`	No	Parameters for the target tool
`id`	No	Task ID (required for cancel)

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

sftp_toolD

ParametersJSON Schema

Name	Required	Description
`serverName`	Yes	SSH server name
`action`	Yes	Action: upload or download
`localPath`	Yes	Local file path (absolute)
`remotePath`	Yes	Remote file path

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

ssh_toolD

ParametersJSON Schema

Name	Required	Description	Default
`serverName`	Yes	SSH server name
`command`	Yes	Command to execute

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

time_toolD

ParametersJSON Schema

Name	Required	Description
`action`	Yes	The operation to perform.
`time_str`	No	An ISO 8601 time string (e.g., '2025-03-15T10:00:00Z'). Required for 'format_time' and 'to_timestamp'.
`timezone`	No	The target timezone (e.g., 'UTC', 'America/New_York', 'Asia/Shanghai').
`timestamp`	No	Unix timestamp in milliseconds. Required for 'from_timestamp'.
`format_options`	No	Formatting options for the time string, based on Intl.DateTimeFormat.

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

workflow_toolD

ParametersJSON Schema

Name	Required	Description	Default
`version`	No	Workflow definition version (e.g., '1.0.1')	1.0
`parallel`	No	If true, executes all steps in parallel.
`steps`	Yes	List of workflow steps
`outputFile`	No	Path to output file (optional)

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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.

10 tool updatesv1.0.0Jan 2, 2026

Changedcalculator_tool51 fields changed

changedInput schema / description

Previous value: -"Calculator tool supporting various math operations."New value: +"A powerful universal calculator supporting basic expressions, statistics, geometry, finance, logic, number theory, combinatorics, probability, set theory, and complex numbers."

changedInput schema / properties / calculation_type / enum

Previous value: -[
-  "evaluate_expression",
-  "calculate_function",
-  "calculate_statistics",
-  "perform_geometry",
-  "perform_financial_math",
-  "perform_logic_operations",
-  "perform_number_theory",
-  "perform_combinatorics",
-  "calculate_probability",
-  "perform_set_theory",
-  "perform_complex_number"
-]New value: +[
+  "evaluate_expression",
+  "calculate_statistics",
+  "perform_geometry",
+  "perform_financial_math",
+  "perform_logic_operations",
+  "perform_number_theory",
+  "perform_combinatorics",
+  "calculate_probability",
+  "perform_set_theory",
+  "perform_complex_number"
+]

removedInput schema / properties / combinatorics_operation / description
```
Removed value: -"The type of combinatorics operation."
```

addedInput schema / properties / complex_a

Added value: +{
+  "description": "First complex number (e.g., '3 + 4i').",
+  "type": "string"
+}

removedInput schema / properties / complex_a_imaginary

Removed value: -{
-  "description": "The imaginary part of the first complex number.",
-  "type": "number"
-}

removedInput schema / properties / complex_a_real

Removed value: -{
-  "description": "The real part of the first complex number.",
-  "type": "number"
-}

addedInput schema / properties / complex_b

Added value: +{
+  "description": "Second complex number (e.g., '1 - 2i').",
+  "type": "string"
+}

removedInput schema / properties / complex_b_imaginary

Removed value: -{
-  "description": "The imaginary part of the second complex number (if needed).",
-  "type": "number"
-}

removedInput schema / properties / complex_b_real

Removed value: -{
-  "description": "The real part of the second complex number (if needed).",
-  "type": "number"
-}

removedInput schema / properties / complex_number_operation / description
```
Removed value: -"The type of complex number operation."
```
removedInput schema / properties / data_points / description
```
Removed value: -"The array of data points."
```

removedInput schema / properties / data_set_x / description

Removed value: -"The dataset X for bivariate statistics."

removedInput schema / properties / data_set_y / description

Removed value: -"The dataset Y for bivariate statistics."

changedInput schema / properties / expression / description

Previous value: -"The mathematical expression to calculate."New value: +"The mathematical expression to evaluate (for 'evaluate_expression')."

removedInput schema / properties / financial_math_operation / description
```
Removed value: -"The type of financial math calculation to perform."
```

removedInput schema / properties / function_argument

Removed value: -{
-  "description": "The argument value for the function.",
-  "type": "number"
-}

removedInput schema / properties / function_name

Removed value: -{
-  "description": "The name of the function to calculate.",
-  "type": "string"
-}

addedInput schema / properties / future_value
```
Added value: +{
+  "type": "number"
+}
```
removedInput schema / properties / geometry_operation / description
```
Removed value: -"The type of geometric calculation to perform."
```

removedInput schema / properties / height

Removed value: -{
-  "description": "The height.",
-  "type": "number"
-}

removedInput schema / properties / length / description
```
Removed value: -"The length."
```
removedInput schema / properties / logic_operation / description
```
Removed value: -"The type of logic operation to perform."
```
removedInput schema / properties / n_compounding_periods / description
```
Removed value: -"The number of compounding periods."
```
removedInput schema / properties / n_value / description
```
Removed value: -"The n value."
```
removedInput schema / properties / number_a / description
```
Removed value: -"The first number."
```
removedInput schema / properties / number_b / description
```
Removed value: -"The second number (if needed)."
```
removedInput schema / properties / number_theory_modulus / description
```
Removed value: -"The modulus for modular exponentiation."
```
removedInput schema / properties / number_theory_operation / description
```
Removed value: -"The type of number theory operation."
```
removedInput schema / properties / operand_a / description
```
Removed value: -"The first operand."
```
removedInput schema / properties / operand_b / description
```
Removed value: -"The second operand."
```
removedInput schema / properties / precision_level / description
```
Removed value: -"Calculation precision level."
```
removedInput schema / properties / principal / description
```
Removed value: -"The principal amount."
```

removedInput schema / properties / probability_a / description

Removed value: -"The probability of event A (between 0 and 1)."

removedInput schema / properties / probability_a_given_b / description

Removed value: -"The conditional probability of A given B (between 0 and 1)."

removedInput schema / properties / probability_b / description

Removed value: -"The probability of event B (between 0 and 1)."

removedInput schema / properties / probability_b_given_a / description

Removed value: -"The conditional probability of B given A (between 0 and 1)."

removedInput schema / properties / probability_operation / description
```
Removed value: -"The type of probability calculation."
```
removedInput schema / properties / r_value / description
```
Removed value: -"The r value (if needed)."
```
removedInput schema / properties / radius / description
```
Removed value: -"The radius of the circle."
```

changedInput schema / properties / rate / description

Previous value: -"The interest rate (percentage)."New value: +"Interest rate as a percentage (e.g., 5 for 5%)."

removedInput schema / properties / set_a / description
```
Removed value: -"The first set."
```

addedInput schema / properties / set_a / items / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / set_a / items / type
```
Removed value: -"number"
```
removedInput schema / properties / set_b / description
```
Removed value: -"The second set."
```

addedInput schema / properties / set_b / items / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / set_b / items / type
```
Removed value: -"number"
```
removedInput schema / properties / set_theory_operation / description
```
Removed value: -"The type of set theory operation."
```
removedInput schema / properties / side / description
```
Removed value: -"The side length of the cube."
```
removedInput schema / properties / statistics_operation / description
```
Removed value: -"The type of statistical calculation to perform."
```

changedInput schema / properties / time / description

Previous value: -"The time (in years)."New value: +"Time in years."

removedInput schema / properties / width / description
```
Removed value: -"The width."
```

Changedcli_tool9 fields changed

changedInput schema / description

Previous value: -"CLI executor with sync/async modes and timeout."New value: +"执行CLI命令，支持同步/异步模式、超时和安全过滤。"

changedInput schema / properties / command / description

Previous value: -"Single-line command content"New value: +"要执行的单行命令"

changedInput schema / properties / commands / description

Previous value: -"Multi-line command sequence (mutually exclusive with 'command')"New value: +"要执行的多行命令序列 (与 'command' 互斥)"

changedInput schema / properties / cwd / description

Previous value: -"Working directory (absolute or relative to build/)"New value: +"命令执行的工作目录 (绝对路径)"

changedInput schema / properties / mode / description

Previous value: -"Execution mode: sync - synchronous blocking, async - asynchronous non-blocking"New value: +"执行模式: sync (同步阻塞), async (异步非阻塞)"

changedInput schema / properties / platform / description

Previous value: -"Force execution context (win32, linux)"New value: +"强制指定执行命令的操作系统环境"

changedInput schema / properties / safe_mode / description

Previous value: -"Enable dangerous command filtering"New value: +"是否启用危险命令过滤"

changedInput schema / properties / timeout / default
```
Previous value: -30New value: +60
```

changedInput schema / properties / timeout / description

Previous value: -"Command timeout in seconds"New value: +"命令执行的超时时间（秒）"

Changedexcel_tool7 fields changed

changedInput schema / description

Previous value: -"Read and write Excel/CSV files"New value: +"Read and write Excel (xlsx) and CSV files, and convert from JSON."

removedInput schema / properties / chunkSize

Removed value: -{
-  "default": 1000,
-  "description": "Chunk size (rows) for streaming",
-  "type": "number"
-}

changedInput schema / properties / filePath / description

Previous value: -"Absolute path to the file"New value: +"Absolute path to the input file"

changedInput schema / properties / format / description

Previous value: -"File format: xlsx, xls, csv"New value: +"File format: xlsx, csv"

changedInput schema / properties / format / enum

Previous value: -[
-  "xlsx",
-  "xls",
-  "csv"
-]New value: +[
+  "xlsx",
+  "csv"
+]

addedInput schema / properties / outputFilePath

Added value: +{
+  "description": "Absolute path to the output file (required for write and convert actions)",
+  "type": "string"
+}

removedInput schema / properties / stream

Removed value: -{
-  "default": false,
-  "description": "Enable streaming for large files",
-  "type": "boolean"
-}

ChangedfileSystem_tool12 fields changed

changedInput schema / description

Previous value: -"Cross-platform file system management tool."New value: +"一个强大的文件系统工具，用于执行读、写、复制、移动、删除、列表等操作。"

addedInput schema / properties / content

Added value: +{
+  "description": "要写入文件的内容 (用于 'write' 操作)",
+  "type": "string"
+}

changedInput schema / properties / fileMode / description

Previous value: -"File mode (permissions) in octal format (e.g., 755)"New value: +"文件模式（权限），使用八进制格式 (例如, 755)"

changedInput schema / properties / gid / description

Previous value: -"Group ID for chown operation"New value: +"用于 chown 操作的组 ID"

changedInput schema / properties / operation / description

Previous value: -"File system operation (read, write, copy, etc.)"New value: +"要执行的文件系统操作 (例如: read, write, copy)"

changedInput schema / properties / overwrite / description

Previous value: -"Overwrite existing files during copy/move"New value: +"在 copy/move 操作中覆盖已存在的文件"

removedInput schema / properties / platformOverride

Removed value: -{
-  "default": "auto",
-  "description": "Override platform for OS behavior simulation",
-  "enum": [
-    "auto",
-    "linux",
-    "win32",
-    "darwin"
-  ],
-  "type": "string"
-}

changedInput schema / properties / recursive / description

Previous value: -"Recursively apply operation to directories"New value: +"递归地对目录应用操作"

changedInput schema / properties / showHidden / description

Previous value: -"Include hidden files/directories in list/listDetails"New value: +"在 list/listDetails 中包含隐藏文件/目录"

changedInput schema / properties / sourcePath / description

Previous value: -"Absolute path to source"New value: +"源文件的绝对路径"

changedInput schema / properties / targetPath / description

Previous value: -"Absolute path to target (required for copy/move)"New value: +"目标文件的绝对路径 (用于 copy/move 操作)"

changedInput schema / properties / uid / description

Previous value: -"User ID for chown operation"New value: +"用于 chown 操作的用户 ID"

Changedimage_tool8 fields changed

changedInput schema / description

Previous value: -"Compress images, batch process files/dirs."New value: +"A powerful image processing tool that supports format conversion, resizing, quality compression, and can batch process directories."

changedInput schema / name

Previous value: -"img_tool"New value: +"image_tool"

addedInput schema / properties / compressionLevel

Added value: +{
+  "default": 6,
+  "description": "PNG compression level (0-9, defaults to 6)",
+  "maximum": 9,
+  "minimum": 0,
+  "type": "number"
+}

changedInput schema / properties / format / description

Previous value: -"Output format"New value: +"Output format (optional, keeps original if not specified)"

removedInput schema / properties / mode

Removed value: -{
-  "default": "sync",
-  "description": "Execution mode (sync or async)",
-  "enum": [
-    "sync",
-    "async"
-  ],
-  "type": "string"
-}

changedInput schema / properties / outputPath / description

Previous value: -"Output directory path (defaults to source)"New value: +"Output directory path. Defaults to a new file (e.g., 'source.processed.jpg') or a new directory (e.g., 'source_processed')."

changedInput schema / properties / quality / default
```
Previous value: -75New value: +80
```

changedInput schema / properties / quality / description

Previous value: -"Compression quality (1-100, defaults to 75)"New value: +"Compression quality for JPEG/WebP/AVIF/TIFF (1-100, defaults to 80)"

Changedlog_tool1 field changed

changedInput schema / required

Previous value: -[
-  "pageSize",
-  "page"
-]New value: +[]

Addedmongo_tool
Addedredis_tool

Changedtime_tool10 fields changed

changedInput schema / description

Previous value: -"Get current time"New value: +"Get and convert time, supporting timezones, formatting, and timestamp operations."

addedInput schema / properties / action

Added value: +{
+  "description": "The operation to perform.",
+  "enum": [
+    "get_current_time",
+    "format_time",
+    "from_timestamp",
+    "to_timestamp"
+  ],
+  "type": "string"
+}

removedInput schema / properties / format

Removed value: -{
-  "description": "Time format (iso, timestamp, local, custom)",
-  "enum": [
-    "iso",
-    "timestamp",
-    "local",
-    "custom"
-  ],
-  "type": "string"
-}

addedInput schema / properties / format_options

Added value: +{
+  "description": "Formatting options for the time string, based on Intl.DateTimeFormat.",
+  "properties": {
+    "day": {
+      "enum": [
+        "numeric",
+        "2-digit"
+      ],
+      "type": "string"
+    },
+    "hour": {
+      "enum": [
+        "numeric",
+        "2-digit"
+      ],
+      "type": "string"
+    },
+    "minute": {
+      "enum": [
+        "numeric",
+        "2-digit"
+      ],
+      "type": "string"
+    },
+    "month": {
+      "enum": [
+        "numeric",
+        "2-digit",
+        "long",
+        "short",
+        "narrow"
+      ],
+      "type": "string"
+    },
+    "second": {
+      "enum": [
+        "numeric",
+        "2-digit"
+      ],
+      "type": "string"
+    },
+    "timeZoneName": {
+      "enum": [
+        "long",
+        "short"
+      ],
+      "type": "string"
+    },
+    "year": {
+      "enum": [
+        "numeric",
+        "2-digit"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

removedInput schema / properties / pattern

Removed value: -{
-  "description": "Custom format pattern (required if format=custom)",
-  "type": "string"
-}

removedInput schema / properties / targetTimezone

Removed value: -{
-  "description": "Target timezone for timestamp conversion (e.g., America/New_York)",
-  "type": "string"
-}

addedInput schema / properties / time_str

Added value: +{
+  "description": "An ISO 8601 time string (e.g., '2025-03-15T10:00:00Z'). Required for 'format_time' and 'to_timestamp'.",
+  "type": "string"
+}

changedInput schema / properties / timestamp / description

Previous value: -"Timestamp to convert"New value: +"Unix timestamp in milliseconds. Required for 'from_timestamp'."

changedInput schema / properties / timezone / description

Previous value: -"Timezone (e.g., Asia/Shanghai)"New value: +"The target timezone (e.g., 'UTC', 'America/New_York', 'Asia/Shanghai')."

changedInput schema / required

Previous value: -[]New value: +[
+  "action"
+]

Changedworkflow_tool2 fields changed

addedInput schema / properties / parallel

Added value: +{
+  "default": false,
+  "description": "If true, executes all steps in parallel.",
+  "type": "boolean"
+}

removedInput schema / properties / steps / items / properties / parallel

Removed value: -{
-  "default": false,
-  "description": "Execute in parallel",
-  "type": "boolean"
-}

15 tool updatesAug 18, 2025
- First observedbuildReload_tool
- First observedcalculator_tool
- First observedcli_tool
- First observedcompress_tool
- First observedcreate_note
- First observedexcel_tool
- First observedfileSystem_tool
- First observedgemini_image_tool
- First observedimage_tool
- First observedlog_tool
- First observedschedule_tool
- First observedsftp_tool
- First observedssh_tool
- First observedtime_tool
- First observedworkflow_tool

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.4/5.0

Scored 2026-04-18 11:01 across 17 tools

Disambiguation2/5

The tools cover diverse domains (e.g., file operations, databases, utilities), but there is significant ambiguity due to vague naming and lack of descriptions. For example, 'image_tool' and 'gemini_image_tool' likely overlap in image-related tasks, while 'cli_tool', 'ssh_tool', and 'sftp_tool' could all involve command-line or remote operations without clear boundaries. The absence of descriptions exacerbates confusion, making it difficult for an agent to reliably choose the right tool for a specific need.

Naming Consistency2/5

Naming conventions are inconsistent and chaotic. There is a mix of styles: some tools use snake_case (e.g., 'calculator_tool', 'create_note'), others use camelCase (e.g., 'fileSystem_tool'), and some have hybrid or irregular forms (e.g., 'buildReload_tool'). Verb usage varies widely, from generic terms like 'tool' to specific verbs like 'create', with no predictable pattern. This inconsistency makes the tool set harder to navigate and understand at a glance.

Tool Count3/5

With 17 tools, the count is borderline high but not extreme, falling into the 16-25 range that feels heavy for a server named 'ToolBox MCP Server', which suggests a broad utility scope. While the number is reasonable for covering multiple domains, it risks being overwhelming without clear organization or descriptions. A more focused set might improve usability, but it doesn't reach the extreme mismatch of 50+ tools.

Completeness2/5

The tool set appears to cover various utility domains (e.g., file systems, databases, scheduling, images), but without descriptions, it's impossible to assess true coverage or identify obvious gaps. The lack of CRUD operations for many domains (e.g., no update/delete for notes or files) and the vague tool names suggest significant gaps in functionality. For instance, 'create_note' might exist, but without tools for reading or managing notes, workflows could hit dead ends, leading to potential agent failures.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Reddit Discussion

Related Servers

Related MCP Connectors

mcp-serverOAuth
com.make
Give your AI agents the tools to build, manage, and run automation workflows.
App Automation Developer Tools Workplace & Productivity
2
SkilderOAuth
ai.skilder
One place to build, share, and govern the skills and tools your AI agents use at work.
Developer Tools CI/CD & DevOps
1
AxiomOAuth
com.axiomide
The marketplace where agents don't just use tools — they build, publish, and compose new ones.
Agent Orchestration Autonomous Agents Developer Tools
1
agentpmtOAuth
com.agentpmt
AI agent marketplace for automated employees, workflows, skills, and tool orchestration.
Agent Orchestration Autonomous Agents App Automation
2

Related MCP Servers

AI Meta MCP Server
Code Execution Autonomous Agents
alxspiker
A
license
A
quality
F
maintenance
Enables AI models to dynamically create and execute their own custom tools through a meta-function architecture, supporting JavaScript, Python, and Shell runtimes with sandboxed security and human approval flows.
Updated a year ago (2025-07-31 20:15 UTC)
5
10
MIT
Jachy MCP Server
Communication App Automation Developer Tools
jachy-h
F
license
A
quality
D
maintenance
A centralized automation hub that provides a unified interface for AI agents to interact with various services, currently featuring Discord forum post creation. It offers an extensible TypeScript architecture designed for easily adding new tool domains and integrating with platforms like Claude Desktop and Cursor.
Updated 7 months ago (2026-03-11 05:29 UTC)
1
-
AutoSpectra MCP Server
Browser Automation API Testing Testing & QA Tools
Skopaq-AI
F
license
Not graded
quality
D
maintenance
All-in-one automation platform for AI agents, providing browser automation, API testing, debugging, and testing tools via the MCP protocol.
Updated a year ago (2025-04-12 16:49 UTC)
3
-
mcp-agent-tools
Agent Orchestration Code Execution Autonomous Agents
CidLucas
F
license
Not graded
quality
D
maintenance
Enables AI agents to execute tools securely with Docker isolation, tier-based permissions, and feature flags, providing a centralized tool registry and MCP server.
Updated 3 months ago (2026-06-26 21:26 UTC)
-

ToolBox MCP 服务器

贡献

特征

工具

资源

工作流工具

提示

开发指南

添加新工具

发展

市场提交

安装

核心价值观

调试

敏感数据

法律责任⚠️

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches