everything-mcp

everything_search

Search files on Windows using Everything's NTFS index. Provide a query, optional path filter, and max results to get matching files.

Instructions

Search files via Everything

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": {
      "query": "<query>"
    },
    "name": "everything_search"
  }
}

Input Schema

Name	Required	Description
`path`	No	Path filter
`query`	Yes	Search query
`maxResults`	No	Max results

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 13, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It merely states 'Search files via Everything' without disclosing whether results are limited by path or maxResults, whether it's read-only (though implied), or what output format is. Lacks behavioral context beyond the verb.

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?

Single sentence, front-loaded, no fluff. Appropriate for a simple search tool.

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?

Description is too sparse for context. No output schema, no annotations; it doesn't explain what the tool returns (file paths? matches?), nor the effect of path/maxResults. Given the tool's complexity relative to information provided, it's incomplete.

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 covers all three parameters with descriptions. The description adds no param semantics; however baseline 3 applies due to 100% schema 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 uses a specific verb ('Search') and resource ('files via Everything'), clearly identifying its function. Sibling tools (everything_count, everything_health) serve different purposes, so this tool is distinct.

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?

No guidance on when to use this tool versus everything_count or everything_health. It doesn't mention scenarios where counting or health checks would be more appropriate.

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

Deploy Server