mcp-tool-verify

Name: mcp-tool-verify
Availability: InStock
Author: siamese001

Verify MCP filesystem write operations and validate tool parameters.

Updated Oct 9, 2025

Search Tags:#error handling #mcp #parameter validation #tool verification #file write #api discipline

Ready to run

npx skills add https://github.com/Siamese001/Agentic-Workflow --skill mcp-tool-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcp-tool-verify
Source: https://github.com/Siamese001/Agentic-Workflow/tree/main/.windsurf/skills/mcp-tool-verify
Command: npx skills add https://github.com/Siamese001/Agentic-Workflow --skill mcp-tool-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents silent failures and unintended consequences from MCP tool calls, ensuring that file operations succeed and only documented parameters are used.

Core Features & Use Cases

Post-Call Verification: Automatically verifies that file write operations (e.g., mcp8_write_file, write_to_file) have actually succeeded by checking file existence and content.
Parameter Validation: Prevents the use of non-existent or hallucinated tool parameters, ensuring API integrity.
Use Case: After an agent writes a configuration file using mcp8_write_file, this Skill immediately checks if the file exists and has content. If not, it attempts a fallback write and reports any persistent failure, preventing downstream errors.

Quick Start

Use the mcp-tool-verify skill to ensure the file 'output.txt' was written successfully after a write operation.

Frequently Asked Questions about mcp-tool-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify that MCP filesystem tool write operations actually succeeded?▼

You can verify MCP filesystem tool write operations by enforcing post-call verification, which checks file existence and content through read-back or stat checks to ensure the write operation succeeded and prevent silent failures.

How do I prevent AI agents from using non-existent or hallucinated MCP tool parameters?▼

To prevent hallucinated MCP tool parameters, you need parameter validation that checks tool calls against documentation or prior successful usage, ensuring API integrity and blocking non-existent parameters from being executed.

What is post-call verification for MCP filesystem tools and when do I need it?▼

Post-call verification for MCP filesystem tools is the process of confirming that file write operations succeeded by checking file existence and content immediately after the call, needed when silent failures could cause downstream errors.

Why does my MCP file write operation report success but leave an empty or missing file?▼

An MCP file write operation may report success while leaving an empty or missing file due to silent failures, which can be caught by post-call verification that checks file existence and attempts a fallback write if content is missing.

Can I use parameter validation to enforce API discipline for MCP tool calls?▼

Yes, you can use parameter validation to enforce API discipline for MCP tool calls by validating parameters against documentation or prior successful usage, preventing the execution of non-existent or invented tool parameters.