skills.rest
SkastVnT
SkastVnTCOMMUNITY
Explore all skills by this author →
GitHub

mcp-tool-authoring

Guide creation and documentation of MCP tools, resources, and prompts.

7|2|Updated Oct 28, 2025
Search Tags:#automation#documentation#integration#mcp#server#chatbot#tools
One-click install
npx skills add https://github.com/SkastVnT/AI-Assistant --skill mcp-tool-authoring
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-tool-authoring
Source: https://github.com/SkastVnT/AI-Assistant/tree/main/.github/skills/mcp-tool-authoring
Command: npx skills add https://github.com/SkastVnT/AI-Assistant --skill mcp-tool-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers to author MCP-related tooling and keep documentation in sync, reducing onboarding time and preventing integration drift.

Core Features & Use Cases

  • Provides a standardized template and workflow for adding MCP tools, resources, and prompts.
  • Enforces contract consistency across tools (input/output shapes, type hints), README updates, and server documentation.
  • Ideal for teams implementing MCP tooling, chatbot route changes, and server-side utilities across the project.

Quick Start

Register a new MCP tool or update an existing one following the templates, then document changes in the MCP README.

Frequently Asked Questions about mcp-tool-authoring

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

FAQPage Schema
How do I add a new tool to an MCP server?▼

Adding a new MCP server tool requires using Python type hints and ensuring JSON-shaped return outputs. You must also update the server README to document the new input and output contracts, preventing integration drift across the project.

What is the correct return format for MCP resources and prompts?▼

MCP resources and prompts must return string values. In contrast, MCP tools are required to return JSON-shaped objects, enforcing a strict contract consistency across your server integration and chatbot routes.

How do I maintain MCP documentation when updating server tooling?▼

Maintaining MCP documentation requires updating the README alongside any server tooling changes. This structured workflow ensures that new tools, modified input contracts, and updated chatbot routes remain fully synchronized with the project documentation.

Can I use this workflow for chatbot route integration with MCP?▼

Yes, this workflow applies directly to developers implementing chatbot route changes and server-side utilities. It provides a standardized template for adding MCP tools and resources while enforcing contract consistency across the integration.

Why do my MCP tool registrations keep drifting from the documentation?▼

Integration drift occurs when MCP tool registrations are updated without synchronizing documentation. Enforcing a structured contract workflow—updating Python type hints, JSON return shapes, and the README simultaneously—prevents this drift.

Related Skills

Explore More Software Engineering Skills→
LerianStudioLerianStudio
205

pre-dev-api-design

Define component interfaces and data contracts before protocol selection.

Official
Basic
joshsmithxrmjoshsmithxrm
5

mcp-verify

Verify MCP tools against a running server via inspector and JSON-RPC calls.

Community
Advanced
BenjaminMichaelisBenjaminMichaelis

add-app-to-server

Add graphical user interfaces to existing MCP tools via HTML resources.

Community
Intermediate
cosmixcosmix
53

documentation

Generate and update code, API, architecture, and user documentation.

Community
Intermediate