add-tool

Add Tool

Add one or more new tools to an existing MCP collection. This skill handles creating the tool file, updating the collection index, and optionally adding integration tests and eval tests.

Use this skill when:

• A new API endpoint has been added and needs a tool
• You want to expose an additional operation from an existing collection
• /build-tools skipped the collection because it already has an index.ts

Prerequisites

Before running, ensure:

1. The collection already exists (src/umbraco-api/tools/{collection}/index.ts)
2. The API client has been generated (src/umbraco-api/api/generated/ exists — if not, run npm run generate)
3. The project compiles: npm run compile

Arguments

• Collection name (required): the collection to add the tool to (e.g. /add-tool form)
• Operation hint (optional): a description of the endpoint to add (e.g. /add-tool form "copy form endpoint")

If no arguments are provided, ask the user which collection and what endpoint to add.

Agents

This skill orchestrates the following agents:

Agent	When to use
mcp-tool-creator	Creating the tool file (Step 3)
mcp-tool-description-writer	Writing the tool description (Step 3)
mcp-tool-reviewer	Reviewing the new tool for LLM-readiness (Step 5)
integration-test-creator	Creating an integration test for the new tool (Step 6)
eval-test-creator	Updating eval tests to cover the new tool (Step 7)

Critical Rules

ONE TOOL AT A TIME. Create one tool file, compile, verify, then move to the next if adding multiple.

RUN COMMANDS SEPARATELY. Always run compile and test as separate Bash calls. Never chain with &&.

DO NOT RECREATE EXISTING INFRASTRUCTURE. The collection index, test setup, builders, and helpers already exist. This skill only adds new files and updates existing ones.

Workflow

Step 0: Understand the Request

Read the arguments to determine:

• Which collection to add to
• What endpoint(s) to add