Skip to main content
Glama
AndersHsueh

AX Local Operations MCP Server

by AndersHsueh

file_edit

Destructive

Edit files at line level to delete, insert, replace, or append content with automatic backup before operations.

Instructions

文件行级编辑:在指定位置删除、插入、替换或追加内容。操作前自动备份原文件。

示例:删除第 3-5 行 { "operation": "delete_lines", "path": "test.js", "start_line": 3, "end_line": 5 } 示例:插入内容到第 2 行后 { "operation": "insert_lines", "path": "test.js", "start_line": 2, "content": "new line" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes编辑操作:delete_lines(删除行)、insert_lines(插入行)、replace_lines(替换行)、append_lines(追加行)
pathYes文件或目录的绝对路径,或相对于 working_directory 的相对路径
start_lineNo起始行号(从1开始)
end_lineNo结束行号(从1开始)
contentNo要写入或追加的文件内容
output_formatNo输出格式:text(纯文本)、json(结构化JSON)、both(两者兼有)
Behavior4/5

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

The description adds valuable behavioral context beyond annotations: it mentions automatic backup before operations, which is crucial for safety given destructiveHint=true. Annotations already indicate it's destructive, non-idempotent, and not read-only, but the backup detail enhances transparency. No contradiction with annotations exists.

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

Conciseness4/5

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

The description is appropriately sized and front-loaded, starting with the core purpose and key behavioral detail (automatic backup). The examples are relevant but could be slightly more concise. Overall, it avoids unnecessary verbosity while being informative.

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

Completeness4/5

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

Given the tool's complexity (destructive operations with 6 parameters) and lack of output schema, the description is reasonably complete. It covers purpose, key behavior (backup), and usage examples. However, it could benefit from mentioning error handling or output details to fully compensate for the missing output schema.

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?

With 100% schema description coverage, the schema fully documents all parameters. The description provides examples that illustrate usage of parameters like operation, path, start_line, end_line, and content, but does not add significant meaning beyond what the schema already specifies. This meets the baseline for high schema coverage.

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

Purpose5/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 as '文件行级编辑' (file line-level editing) with specific operations: delete, insert, replace, or append content. It distinguishes itself from sibling tools like file_operation, file_compare, and file_search by focusing on line-level modifications rather than general operations, comparisons, or searches.

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

Usage Guidelines4/5

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

The description provides clear context for usage with examples for delete and insert operations, implying when to use this tool for line-level edits. However, it does not explicitly state when not to use it or mention alternatives among sibling tools (e.g., using file_operation for non-line-level edits or file_compare for comparisons).

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

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/AndersHsueh/Ax-LocalTools-MCP'

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