new-tool
Skill3 starsChanged 8 months agoMITView on GitHub
Follow this exact pattern when adding a new tool. Do not invent new registration patterns or file structures.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- TobiasMue91/tobiasmue91.github.iotheir own version, first seen Nov 1, 2026
- jamesmccomish/mp-mcptheir own version, first seen Oct 20, 2026
- OpenC3/cosmostheir own version, first seen Oct 8, 2026
- ShenSeanChen/waku-agenttheir own version, first seen Oct 8, 2026
- wnkinc/claude-custom-connector-servertheir own version, first seen Jul 16, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- ShenSeanChen/waku-agent★ 2.2ksame name
- OpenC3/cosmos★ 261same name
- TobiasMue91/tobiasmue91.github.io★ 59same name
- jamesmccomish/mp-mcp★ 2same name
- wnkinc/claude-custom-connector-server★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Follow this exact pattern when adding a new tool.
- Very specific: line 9
Add the handler inside the existing register*Tools(server, exchangeManager) function
- Very specific: line 13
If you created a new category file, import and call its register*Tools() function here
- Distinctive: line 17
Add the tool to the tools table with name, description, and parameters
- Very specific: line 21
Add the tool name to the appropriate tier in TOOL_PRICING
- Distinctive: line 25
Test parameter validation and expected output shape
- Very specific: line 28
Create new files under src/ for a single tool — add to the matching category file
- Very specific: line 29
Use require() — this project is ESM (NodeNext)
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Adding a New MCP Tool
Follow this exact pattern when adding a new tool. Do not invent new registration patterns or file structures.
Steps
- Implement in
src/tools/<category>.ts- Define a Zod schema for the tool's parameters using validators from
src/utils/validators.ts - Add the handler inside the existing
register*Tools(server, exchangeManager)function - Return
{ content: [{ type: 'text', text: JSON.stringify(...) }] }
- Define a Zod schema for the tool's parameters using validators from
- Register in
src/tools/index.ts- If you created a new category file, import and call its
register*Tools()function here - Existing categories (market-data, account, trading, cardano, strategy) are already wired up
- If you created a new category file, import and call its
- Update README.md
- Add the tool to the tools table with name, description, and parameters
- Assign a pricing tier: free (
list_exchangesonly), read ($0.001), or write ($0.01)
- Add pricing in
src/payment/index.ts- Add the tool name to the appropriate tier in
TOOL_PRICING
- Add the tool name to the appropriate tier in
- Add unit test in
src/tests/- Mock the exchange connector via
getConnectorSafe() - Test parameter validation and expected output shape
- Mock the exchange connector via
Do NOT
- Create new files under
src/for a single tool — add to the matching category file - Use
require()— this project is ESM (NodeNext) - Skip
npm run typecheckafter changes
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

