Skip to main content
Glama

JSON/模板操作

item_operations

Perform CRUD operations on JSON data and templates, including creation, retrieval, editing, deletion, and statistical analysis. Supports advanced querying, node-level editing, and tag-based filtering for efficient JSON management.

Instructions

通用工具,用于创建、获取、列表、编辑、删除JSON或模板,以及获取统计信息。支持完整的CRUD操作和高级查询功能。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes操作类型:create(创建)、get(获取)、list(列表)、edit(编辑)、delete(删除)、stats(统计)
categoryNo分类:模板的分类,如'user'、'product'、'config'等
contentNo内容:JSON字符串,必须是有效的JSON格式。示例:{"key":"value"}
descriptionNo描述:项目的详细说明,帮助理解项目用途
filter_tagsNo标签筛选:只显示包含指定标签的JSON,如['user', 'active']
filter_typeNo类型筛选:all(全部)、generated(批量生成)、manual(手动创建)
idNo项目ID:用于get、edit、delete操作,必须是已存在的ID
indexNo数组索引:add/remove操作时的位置索引,从0开始。不指定则添加到末尾或删除第一个
item_typeNo项目类型:json(JSON数据) 或 template(模板),除stats外都需要指定
limitNo列表限制:返回的最大项目数量,默认20,最大100
nameNo名称:创建时的项目名称,建议使用有意义的描述性名称
operationNo编辑操作:set(设置值)、add(添加元素)、remove(删除)、update(更新对象)
pathNo节点路径:编辑JSON时的路径,支持点号分隔。示例:'users.0.name'、'config.database.host'
sort_byNo排序方式:createdAt(创建时间)、updatedAt(更新时间)、name(名称)、size(大小)
tagsNo标签:JSON项目的分类标签,如['user', 'config', 'test']
valueNo新值:要设置、添加或更新的值。可以是任何类型:字符串、数字、数组、对象等
variablesNo变量:模板中的变量名列表,如['name', 'age', 'email']
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'CRUD operations' and 'advanced query', but fails to describe critical behaviors like authentication needs, rate limits, error handling, or what 'stats' returns. For a tool with 17 parameters and multiple actions, this leaves significant gaps in understanding how it behaves.

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

Conciseness3/5

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

The description is a single sentence that efficiently lists capabilities ('create, get, list, edit, delete, stats') and mentions 'CRUD operations and advanced query'. However, it's front-loaded with a broad claim ('通用工具') and could be more structured to highlight key use cases or differentiate from siblings, making it adequate but not optimally concise.

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's high complexity (17 parameters, 6 actions), no annotations, and no output schema, the description is insufficient. It doesn't explain return values, error conditions, or behavioral nuances like how 'edit' with 'operation' works. The agent must rely heavily on the input schema, leaving gaps in understanding the tool's full context.

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 schema description coverage is 100%, so the schema already documents all 17 parameters thoroughly with descriptions and enums. The description adds no additional parameter semantics beyond what's in the schema, such as explaining dependencies between parameters (e.g., 'id' is required for 'get' but not 'create'). Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose3/5

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

The description states the tool performs 'CRUD operations and advanced query functions' on 'JSON or templates', which gives a general purpose. However, it's vague about what specific resources it operates on ('JSON or templates' is broad) and doesn't distinguish from sibling tools like 'batch_generate_json' or 'export_to_file'—it's unclear when to use this versus those alternatives.

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 versus its siblings ('batch_generate_json', 'export_to_file'). The description mentions 'advanced query function' but doesn't specify contexts or exclusions, leaving the agent to infer usage from the parameter schema alone.

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

Install Server

Other Tools

Related Tools

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/zb2947244682/mcp-json-maker'

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