mcp-change

Synchronize an existing FOUNDATION MCP tool across Rust handler, template, and ontology.

19|3|Updated Jul 19, 2024

Search Tags:#ontology #dispatch #mcp #rust #tool #code-sync

Ready to run

npx skills add https://github.com/danielterra/FOUNDATION --skill mcp-change

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcp-change
Source: https://github.com/danielterra/FOUNDATION/tree/main/.claude/skills/mcp-change
Command: npx skills add https://github.com/danielterra/FOUNDATION --skill mcp-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps an existing Foundation MCP tool aligned across the Rust handler, the ToolTemplate, and the MCPTool ontology when changes are needed, preventing drift between implementation and semantics.

Core Features & Use Cases

Synchronize the Rust handler logic with the ToolTemplate and the MCPTool ontology.
Update the parameters, description, and input/output schemas in a coordinated, single-change workflow.
Validate consistency by re-checking code, definitions, and ontology after edits.

Quick Start

Identify the MCPTool, update the Rust handler and definitions, extend the input/output schemas, and refresh the ontology to match the new tool configuration.

Frequently Asked Questions about mcp-change

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

FAQPage Schema

How do I keep an MCP tool ontology in sync with Rust handler changes?▼

To sync an MCP tool ontology with Rust handler changes, you update the handler, ToolTemplate, and MCPTool ontology together in a single workflow. This prevents semantic drift between implementation and ontology definitions.

What is the best way to update MCP tool input and output schemas in Rust?▼

Updating MCP tool input and output schemas in Rust requires extending the schemas in the handler and ToolTemplate. You must then refresh the MCPTool ontology to match the new configuration and validate with cargo check.

Why does my MCP tool definition drift after updating Rust handler parameters?▼

MCP tool definition drift occurs when Rust handler parameters are updated without corresponding changes to the ToolTemplate and MCPTool ontology. Maintaining parity across all three components prevents semantic misalignment.

How do I validate MCP tool consistency after modifying an ontology schema?▼

To validate MCP tool consistency after modifying an ontology schema, you re-check the code, definitions, and ontology for parity. You must run cargo check to validate the Rust handler before declaring the update done.

Can I update an existing Foundation MCP tool without breaking the ontology?▼

You can update an existing Foundation MCP tool without breaking the ontology by applying parameter changes across the Rust handler, ToolTemplate, and MCPTool ontology simultaneously. This coordinated workflow ensures definitions remain aligned.