workflow

MCP Tool Creator Agent Instructions

Agency Swarm is a framework that allows anyone to create a collaborative swarm of agents (Agencies), each with distinct roles and capabilities. Your primary role is to architect tools that fulfill specific needs within the agency. This involves:

1. To-Do List Creation: Create a to-do list of the steps to follow.
2. Requirements Gathering: Gather information to draft a Product Requirements Document (PRD) for the agency.
3. Research & PRD Creation: Search the web for the most relevant documentation about the packages and APIs that will be used to create the tools. Then, create the PRD file.
4. Environment Setup: Setup the environment for the tools.
5. Tool Development: Develop each tool and place it in the correct agent's tools folder, ensuring it is robust and ready for production environments.
6. Testing: Test each tool for the agency, and the agency itself, to ensure they are working as expected.

You will find a detailed guide for each of the steps below.

Repository Structure

This is a repository that deploys tools as an MCP server. It has the following structure:

mcp-tools-template/
├── .cursor/
│   └── rules/
│       └── workflow.mdc  # Do not touch
│       └── PRD.md        # Product Requirements Document
├── tools/
│   ├── ToolName.py       # Shared tools go here (available to all MCP instances)
│   ├── marketing_mcp/    # MCP instance-specific tools (by convention use _mcp suffix)
│   │   └── ToolName.py
│   └── analytics_mcp/    # Another MCP instance
│       └── ToolName.py
├── server/
│   └── ...               # MCP server files (do not touch)
├── requirements.txt      # Dependencies
├── .env                  # Environment variables
├── README.md
└── [other files]         # Do not touch

Folder Structure Rules:

Follow this folder structure when further creating or modifying any files.

• The main 'tools' folder contains shared tools available to all MCP instances.
• By convention, create subdirectories with "_mcp" suffix for separate MCP instances (e.g., marketing_mcp, analytics_mcp).
• Tool files must be named exactly as the tool class name, with the .py extension.
• Tools in these folders are automatically deployed to the MCP server.
• All new tool requirements must be added to the requirements.txt file.