Skip to main content
Glama
Sign In
ellmos-filecommander-mcp

ellmos-filecommander-mcp

by ellmos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search File Content

fc_search_content
Read-onlyIdempotent

Durchsucht ausschließlich explizit übergebene Dateien nach Text. Standardmäßig literal, optional mit regulärem Ausdruck; deterministische begrenzte JSON-Ausgabe, dateibezogene Teilfehler, Binärdatei-Skip, Kontextzeilen und…

Instructions

Durchsucht ausschließlich explizit übergebene Dateien nach Text. Standardmäßig literal, optional mit regulärem Ausdruck; deterministische begrenzte JSON-Ausgabe, dateibezogene Teilfehler, Binärdatei-Skip, Kontextzeilen und Geheimnis-Redaktion. Keine Glob-Auflösung und keine Verzeichnisrekursion.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "paths": "<paths>",
      "query": "<query>"
    },
    "name": "fc_search_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesExplicit file paths in result order; directories and glob patterns are not expanded
queryYesLiteral text by default, or a regular expression when regex=true
regexNoInterpret query as a regular expression
max_resultsNoGlobal match limit
context_linesNoContext lines before and after each match
case_sensitiveNoUse case-sensitive matching
max_results_per_fileNoMatch limit per file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.11.5

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses important behavior: deterministic bounded JSON output, per-file partial errors, binary-file skipping, context lines, and secret redaction. These are meaningful operational traits an agent would not otherwise know.

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

Conciseness5/5

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

The description is dense but front-loaded: the core scope is stated first, followed by the key limitations. Every clause adds relevant information with no filler.

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

Completeness5/5

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

With seven parameters, full schema coverage, and no output schema, the description supplies the missing behavioral context, including output form, partial errors, binary handling, and redaction. An agent has enough information to call the tool correctly.

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 every parameter is already documented in the schema. The description reinforces default literal matching and optional regex behavior, but does not add substantial parameter-level meaning beyond the schema; this is the baseline case for high 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 states a specific verb and resource: searching explicitly passed files for text. It also clearly delimits scope by saying there is no glob expansion and no directory recursion, which distinguishes it from broader search siblings such as fc_search_files.

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?

It clearly establishes the condition for using this tool: only explicitly supplied file paths are searched. The exclusions for globs and directory recursion are helpful, but no sibling tool is named as the alternative for those cases, so it falls short of explicit alternative routing.

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