tool-set-enabled-state

Enable or disable multiple MCP tools in batch mode.

Updated Aug 26, 2025
One-click install
npx skills add https://github.com/infotechsrealm/PanicAtThePond --skill tool-set-enabled-state-infotechsrealm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-set-enabled-state
Source: https://github.com/infotechsrealm/PanicAtThePond/tree/main/.claude/skills/tool-set-enabled-state
Command: npx skills add https://github.com/infotechsrealm/PanicAtThePond --skill tool-set-enabled-state-infotechsrealm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows for the batch enablement or disablement of Multiple Core Plugins (MCP) tools, with the changes persisting only if at least one tool's state is actually changed.

Core Features & Use Cases

  • Batch Tool State Management: Enable or disable multiple MCP tools simultaneously.
  • Persistence: Changes are saved only if at least one tool's state has been altered.
  • Use Case: If you want to quickly enable or disable a set of tools for your AI agent without manually changing each one, this Skill can automate the process.

Quick Start

Use the tool-set-enabled-state skill to enable the 'Pathfinding' and 'Navigation' tools for your AI agent.

Frequently Asked Questions about tool-set-enabled-state

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

FAQPage Schema
How do I batch enable or disable MCP tools for an AI agent?

You can batch enable or disable MCP tools by modifying the state of Multiple Core Plugins simultaneously. This automates tool configuration for AI agents without manually changing each tool individually.

Does MCP tool state persistence require a specific save function?

MCP tool state persistence requires calling UnityMcpPluginEditor.Instance.Save() to apply changes. The configuration is saved only if at least one tool's state has actually been modified during the batch operation.

Can I use this batch tool management approach for Unity plugin configurations?

Yes, batch tool management is designed for Unity plugin configurations. It manages Multiple Core Plugins tools in batch mode to automate tool state changes for AI agents operating within the Unity environment.

What happens if no MCP tool state is modified during the batch operation?

If no MCP tool state is modified, changes will not persist. The system ensures that persistence only occurs when at least one tool's state is actually altered, preventing unnecessary save operations.

When do I need batch tool state management for AI agent configuration?

You need batch tool state management when you want to quickly enable or disable a set of MCP tools for your AI agent. It replaces the manual effort of changing each tool state individually.