Skip to main content
Glama
Systems Manager

Systems Manager

Manage File

sm_file_manage_file
Destructive

Read, create, update, or delete files and logs on managed systems, with optional confirmation for destructive actions.

Instructions

Manage file (sm_file_operations). Operations for file and log management

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sm_file_manage_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.
contentNoContent to create or update the file with
filepathNoPath to file
file_actionNoAction for text editor/manage fileread

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the description's job is to add context such as what gets destroyed, whether delete is irreversible, or how confirmation works. It adds none of this; the only extra word ("log") actually muddies scope by implying log handling that sibling tools own.

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?

Two very short sentences with no filler, so nothing is padded, but the brevity comes from under-specification rather than precision. The parenthetical internal name and the vague category phrase do not earn their place as much as a single concrete scope sentence would.

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?

This is a destructive, non-idempotent, multi-action file tool with four parameters and no output schema, so the description carries a heavy load. It omits the action model, the meaning of confirm for destructive calls, and any return-value expectation, leaving the schema alone to explain a risky write operation.

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?

Schema coverage is 100%, so all four parameters including file_action, filepath, content and confirm are documented in the schema. The description adds no meaning beyond it, which is acceptable at the baseline but leaves nothing compensable for the destructive semantics of file_action=delete.

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

Purpose2/5

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

"Manage file" restates the tool name and title almost verbatim; "Operations for file and log management" is a generic category label rather than a described capability. It never says what actually gets managed (read, create, update, delete) even though the enum in the schema lists exactly those actions, and it does not differentiate from siblings such as sm_file_grep_files, sm_file_list_files or sm_file_tail_log_file.

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?

There is no guidance on when to choose this tool over the sibling file tools (list, search, grep, tail log) or when to avoid it. The only implied usage is the vague phrase "file and log management", which arguably steers an agent toward duplicating log tools that already exist as siblings.

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

Deploy Server

Other Tools