ShareWatch

Search Files

search_files

Read-onlyIdempotent

Search for files by name, text content, type, or date range. Use this instead of list_files when the user has many files or is looking for something specific. Use content when the user remembers what a file says but not what it is called. All parameters are optional — combine them to narrow results. Searches only what the user has shared with ShareWatch, and a shared folder does not share its contents — files inside it must be shared themselves.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Filter by file type. One of: document, spreadsheet, presentation, pdf, folder. Matched case-insensitively; any other value is REJECTED with an error rather than ignored, so a filter you set is always a filter that applied.
`query`	No	Search by file name (partial match). Example: 'board deck' or 'Q3 financials'
`content`	No	Search inside file text, not just names — finds files whose body contains these words, scoped to files ShareWatch can see. Word-based, not substring: 'quarterly revenue' matches files containing those words. Combine with query to require both.
`modified_after`	No	Only files modified after this date (ISO 8601 e.g. '2026-01-01')
`modified_before`	No	Only files modified before this date (ISO 8601 e.g. '2026-04-01')

Output Schema

TableJSON Schema

Name	Required	Description	Default
`files`	Yes
`guidance`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 11, 2026

addedOutput schema / properties / files / items / properties / account

Added value: +{
+  "description": "the account this file lives in, when the user has connected more than one — pass it back as account on create tools to put new files there",
+  "type": "string"
+}

addedOutput schema / properties / files / items / properties / provider

Added value: +{
+  "description": "the provider of that account: google",
+  "type": "string"
+}

Changed2 schema fields changedSep 10, 2026
- removedOutput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / files / items / additionalProperties
```
Removed value: -false
```
First observedSep 5, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already mark it read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds valuable behavioral context: searches are scoped to explicitly shared files, and a shared folder does not imply its contents are shared.

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 compact and front-loaded with the main purpose, followed by differentiation and important scope caveats. Every sentence adds distinct value without unnecessary padding.

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?

Given the rich schema, an output schema, and safety annotations, the description covers what an agent needs: purpose, when to use it, how to combine parameters, and the critical sharing scope limitation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema carries most parameter meaning. The description adds useful aggregate semantics by noting all parameters are optional and can be combined to narrow results, which goes beyond a simple restatement.

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?

Description names a specific action (search), the object (files), and the dimensions (name, text content, type, date range). It also distinguishes itself from list_files, making it clear what this tool is for.

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

Usage Guidelines5/5

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

Explicitly says to use this instead of list_files when the user has many files or is looking for something specific. It also gives parameter-level guidance on when to use content search, which helps an agent choose the right approach.

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

All ShareWatch tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?