windy-word-mcp

export_soul_file_to_path

Export your Windy Word archive (audio, video, transcripts) as a zip to a specified path for backup or digital-twin use. Includes manifest with stats.

Instructions

Export the user's entire Windy Word archive (audio + video + transcripts) as a single zip file at the given path. The Forma Animae artifact — Grant's exportable "soul" for use with the Windy Clone digital-twin pipeline or as a portable backup. Includes a manifest.json with stats (file counts, word counts, date range). Refuses to overwrite existing files unless overwrite=true. Creates parent directories as needed. Pairs with the existing export-soul-file IPC the renderer uses via the Soul File button (which opens a save dialog) — this is the path-based variant for agent-driven exports.

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": {
      "outputPath": "<outputPath>"
    },
    "name": "export_soul_file_to_path"
  }
}

Input Schema

Name	Required	Description	Default
`overwrite`	No	If true, replace existing file. Default false.
`outputPath`	Yes	Destination .zip path (e.g. "/home/user/Documents/my-soul-2026-05.zip").

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?

With no annotations provided, the description fully explains behavioral traits: it refuses overwrite by default, creates parent directories as needed, and includes a manifest with stats. It also explains the semantic 'soul' concept and its pipeline use, offering complete transparency.

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 concise (5 sentences) and front-loaded with the action. Each sentence adds unique information, though the second sentence on 'Forma Animae artifact' introduces jargon that slightly reduces clarity for general agents. No wasted content.

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 no output schema, the description adequately covers return behavior (zip file with manifest), file handling (overwrite, directory creation), and the input schema has only two well-documented parameters. All essential aspects are addressed for effective use.

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 baseline is 3. The description adds value by explaining the effect of overwrite ('refuses to overwrite... unless overwrite=true') and clarifying outputPath as a destination .zip path, which reinforces parameter meaning beyond the schema.

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 identifies the tool's action ('export the entire Windy Word archive as a single zip file'), specifies the output format and contents (audio, video, transcripts, manifest.json), and distinguishes it from the sibling save-dialog variant via 'path-based variant for agent-driven exports.'

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?

The description explicitly notes the tool's default refusal to overwrite and condition to allow it (overwrite=true), and contrasts it with the related IPC variant. It provides clear context for use (agent-driven exports) but does not list exhaustive alternatives or non-use cases.

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

Deploy Server