Skip to main content
Glama
Systems Manager

Systems Manager

Search Files

sm_file_search_files
Read-onlyIdempotent

Search files by pattern and path to locate matching files for file and log management tasks.

Instructions

Search 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_search_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternNoSearch pattern
filepathNoPath to file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that - it does not say whether the pattern matches file names, paths, or file contents, nor whether results are paginated or capped. That leaves the most important behavioral ambiguity of a search tool unresolved.

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?

It is short and front-loaded, which is good, but the second sentence is pure filler that duplicates module context and earns no place in a tool-level description. The brevity here reflects under-specification rather than disciplined editing.

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 search tool with two optional parameters, the definition never resolves what is being searched or how results are shaped, and it provides no differentiation from the grep sibling. Annotations and full schema coverage compensate partially, but an agent still cannot confidently choose or invoke this tool from the description alone.

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 both parameters (pattern, filepath) are documented in the schema and the baseline is 3. The description does not clarify the syntax of "pattern" (glob, regex, substring) or how it relates to "filepath," but it is not required to given full schema coverage.

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 is essentially the name restated: "Search files" adds no scope, no target (filenames vs. file contents), and no distinguishing trait versus the sibling sm_file_grep_files or sm_file_list_files. The second sentence, "Operations for file and log management," is a module-level tagline rather than a statement of what this tool does.

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

Usage Guidelines1/5

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

There is no when-to-use guidance at all: no indication of when to pick search over grep or list, no prerequisites, and no note on when this tool is inappropriate. With a near-identical sibling (sm_file_grep_files) present, the absence of routing guidance is a serious omission.

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