MCP JSON Maker
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| item_operationsC | 通用工具，用于创建、获取、列表、编辑、删除JSON或模板，以及获取统计信息。支持完整的CRUD操作和高级查询功能。 |
| batch_generate_jsonB | 根据模板和规则批量生成JSON数据。支持基于现有模板生成或根据规则动态生成。适用于测试数据生成、批量数据处理等场景。 |
| export_to_fileB | 将JSON数据导出到指定文件，支持多种格式和插入位置。支持绝对路径和相对路径，自动创建不存在的目录。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The tools have distinct primary purposes—batch generation, file export, and CRUD operations—but 'item_operations' is overly broad and could overlap with the others, especially since it handles JSON/template CRUD which might include generation or export-like functions. Descriptions help clarify, but the boundaries are somewhat fuzzy.
The naming is mixed: 'batch_generate_json' and 'export_to_file' follow a verb_noun pattern, but 'item_operations' uses a vague noun-based style. This inconsistency makes the set less predictable, though the names are still readable and not chaotic.
With 3 tools, the count is reasonable for a JSON-focused server, though it feels slightly thin for covering all aspects of JSON manipulation. Each tool appears to serve a distinct role, so it's well-scoped but could benefit from more granularity in some areas.
The tools cover key areas: generation, export, and CRUD operations, providing good lifecycle coverage for JSON data. However, there are minor gaps, such as no dedicated tool for JSON validation or transformation, which agents might need to work around using the existing tools.