windy-word-mcp

scan_folder_for_media

Scan a folder to find all audio and video files, returning per-file details and aggregate statistics like total count and duration.

Instructions

Scan a folder for audio + video files (recursive by default). Use this when the user says "find all my voice memos", "what recordings do I have in this folder", "look in my Music folder", or before bulk_ingest_to_clone so the agent knows what's there. Returns per-file { path, name, ext, sizeBytes, modifiedAt, kind, durationSec? } plus aggregates (audioCount, videoCount, totalSizeBytes, totalDurationSec). Audio durations are extracted via music-metadata. Capped at 500 results to prevent runaway responses (truncated:true in that case); recursion depth capped at 6 to prevent symlink loops. Permission-denied subdirectories are silently skipped. Read-only — no side effects.

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": {
      "path": "<path>"
    },
    "name": "scan_folder_for_media"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Absolute or tilde-expanded folder path to scan.
`recursive`	No	Walk subdirectories. Defaults true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.11.0Jul 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

No annotations provided, but description fully discloses behavior: recursive by default, capped at 500 results, recursion depth 6, permission-denied subdirectories silently skipped, read-only, and audio duration extraction method. No contradictions.

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

Conciseness4/5

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

The description is somewhat lengthy but every sentence adds value. It is well-structured with usage hints first, then return details and constraints. Could be slightly more concise but is not verbose.

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?

No output schema, but the description fully explains return format (per-file fields and aggregates), truncation flag, and edge cases (permission-denied, loops). Complete for a scanning tool with two simple parameters.

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 coverage is 100% with descriptions for both parameters. The description reiterates defaults (recursive default true, path expansion) but adds minimal new meaning beyond what schema already provides.

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 clearly states it scans a folder for audio/video files recursively, provides example user queries, and mentions its use before bulk_ingest_to_clone. It distinguishes from siblings by being the only scanning tool among them.

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 'Use this when the user says...' and gives context for before bulk_ingest_to_clone. Also mentions behavioral limits like 500 results cap and recursion depth 6, guiding appropriate use.

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

Deploy Server