Skip to main content
Glama
Systems Manager

Systems Manager

Grep Files

sm_file_grep_files
Read-onlyIdempotent

Search a file or directory for a specified text pattern, optionally recursively, to locate matching content in files and logs.

Instructions

Grep 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_grep_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternNoSearch pattern
filepathNoPath to file
recursiveNoRecursive search

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.5/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 elsewhere. The description adds nothing beyond that - no note on whether results are truncated, whether binary files are skipped, or how pattern syntax is interpreted - and the 'file and log management' sentence is filler.

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, so nothing is bloated, but the second sentence ('Operations for file and log management') earns no place and the front-loaded content is only a restated title. Brevity here reflects under-specification rather than tight 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?

With three optional parameters, no output schema, and behavior that materially depends on how pattern and filepath interact with recursive, the description leaves the agent without enough to call it confidently. Rich annotations cover safety but not semantics, and nothing here explains what a grep result looks like.

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 pattern, filepath and recursive are each documented in the input schema and the baseline applies. The description contributes no additional meaning, such as whether pattern supports regex or whether filepath may be a directory when recursive is set.

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 phrase 'Grep files' names a recognizable verb and resource, so an agent can infer this searches file contents for a pattern. However, it offers no differentiation from the sibling sm_file_search_files, and the trailing '(sm_file_operations)' plus 'Operations for file and log management' are category labels rather than purpose statements.

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 sm_file_search_files or sm_file_get_system_logs, no prerequisites, and no exclusions. The agent must infer the use case entirely from the name.

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