Skip to main content
Glama
Sign In
mac2win-zip MCP Server

mac2win-zip MCP Server

by Wordbe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

validate_zip_for_windows

Checks ZIP files for Windows compatibility, flagging forbidden characters and Unicode naming issues to prevent extraction errors.

Instructions

Validate if a ZIP file is Windows-compatible.

Args: zip_path: Path to the ZIP file to validate working_dir: Base directory for relative path

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": {
      "zip_path": "<zip_path>"
    },
    "name": "validate_zip_for_windows"
  }
}

Input Schema

NameRequiredDescriptionDefault
zip_pathYes
working_dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 must disclose side effects and return values. It only says 'Validate' without explaining the output, error behavior, or whether it modifies anything.

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 succinct and front-loaded with a clear purpose statement, followed by a structured parameter list. Every sentence adds value.

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?

The description lacks essential context: no return value, no validation criteria, and no output schema. It is too sparse for a tool with no annotations or schema hints.

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?

The description includes an Args section that explains 'zip_path' and 'working_dir', which supplements the schema where descriptions are absent. However, the explanation is minimal and doesn't clarify how 'working_dir' affects validation.

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 the tool's function with a specific verb ('Validate') and resource ('a ZIP file'), and the scope 'Windows-compatible' distinguishes it from the sibling tool 'create_windows_compatible_zip'.

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?

There is no explicit guidance on when to use this tool vs the sibling tool. The description only states what it does, not when to prefer it.

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