Skip to main content
Glama
Systems Manager

Systems Manager

List Files

sm_file_list_files
Read-onlyIdempotent

Lists files and directories at a specified path or remote host, with optional recursive search and depth control for file and log management.

Instructions

List files (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_list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoDepth for list_files
filepathNoPath to file
recursiveNoRecursive search

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?

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context such as what listing returns, how recursion behaves, or whether hidden files are included.

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 short, but the parenthetical tool-family reference and the generic "Operations for file and log management" sentence add little value. It is concise but not front-loaded with useful scoping information.

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?

For a file-listing tool with three optional parameters and no output schema, the description is too thin. It does not explain the listing scope, recursion behavior, or how it differs from the many sibling file tools.

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 description coverage is 100%, so the schema already documents depth, filepath, and recursive. The description adds no meaning beyond those parameter definitions, which is the baseline expectation when schema coverage is complete.

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?

The description essentially restates the tool name and title: "List files." The added phrase "Operations for file and log management" is a generic category, not a specific scope, and it does not distinguish this tool from siblings like sm_file_search_files or sm_file_grep_files.

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 use this tool versus search_files, grep_files, or manage_file. It also gives no conditions, exclusions, or prerequisites for listing files.

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