torbjorn/my-pal-mcp-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: rebranding, see [docs/name-change.md](docs/name-change.md) for details

Browse Source
This commit is contained in:
Fahad
2025-12-04 18:11:55 +04:00
parent bcfaccecd4
commit b2dc84992d
122 changed files with 1423 additions and 1056 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/adding_tools.md
View File

@@ -1,6 +1,6 @@
# Adding Tools to Zen MCP Server
# Adding Tools to PAL MCP Server
Zen MCP tools are Python classes that inherit from the shared infrastructure in `tools/shared/base_tool.py`.
PAL MCP tools are Python classes that inherit from the shared infrastructure in `tools/shared/base_tool.py`.
Every tool must provide a request model (Pydantic), a system prompt, and the methods the base class marks as
abstract. The quickest path to a working tool is to copy an existing implementation that matches your use case
(`tools/chat.py` for simple request/response tools, `tools/consensus.py` or `tools/codereview.py` for workflows).
@@ -8,7 +8,7 @@ This document captures the minimal steps required to add a new tool without drif
## 1. Pick the Tool Architecture
Zen supports two architectures, implemented in `tools/simple/base.py` and `tools/workflow/base.py`.
PAL supports two architectures, implemented in `tools/simple/base.py` and `tools/workflow/base.py`.
- **SimpleTool** (`SimpleTool`): single MCP call – request comes in, you build one prompt, call the model, return.
The base class handles schema generation, conversation threading, file loading, temperature bounds, retries,