26 replies

Custom tools within Plugin not recognized

✅Solved

Problem:
The custom tools (

paper_trade_buy

paper_trade_buy

get_portfolio_risk

get_portfolio_risk

) within the

execution-plugin

execution-plugin

are not being recognized by OpenClaw. Despite following the plugin creation process successfully for the

market-data-plugin

market-data-plugin

(which now works), the

execution-plugin

execution-plugin

consistently fails with "tool not found" or "tool not available" errors.

Troubleshooting Steps Taken:

1. Initial Setup:
* Created plugin directory: .openclaw\extensions\execution-plugin


    *   Created


    *   Created

package.json

 with

 with

name

version

main: "index.js"

type: "module"

, and

, and

dependencies

node-fetch

).
    *   Created

).
    *   Created

openclaw.plugin.json

 manifest. Initially,

 manifest. Initially,

 was "execution", but later corrected to "execution-plugin" to match the directory name and

 was "execution", but later corrected to "execution-plugin" to match the directory name and

openclaw.json

 entry.
    *   Created

 entry.
    *   Created

index.js

 with the

 with the

export default function(api)

 structure and implemented

 structure and implemented

paper_trade_buy_execute

and

and

get_portfolio_risk_execute

 functions, registering them with

 functions, registering them with

api.registerTool

.
    *   Installed dependencies using

.
    *   Installed dependencies using

npm install --prefix

.
    *   Enabled the plugin in

.
    *   Enabled the plugin in

openclaw.json

plugins.entries["execution-plugin"].enabled = true

).
    *   Moved the plugin from

).
    *   Moved the plugin from

plugins

to

to

extensions

 directory.

2.  *API Key Configuration (for context, though not directly related to tool *recognition*):*
    *   The

 directory.

2.  *API Key Configuration (for context, though not directly related to tool *recognition*):*
    *   The

POLYGON_API_KEY

 was correctly set in

 was correctly set in

.openclaw/.env

 and applied via

 and applied via

gateway.config.patch

 and later direct edit to

 and later direct edit to

openclaw.json

 to resolve tool invocation issues for other plugins.
    *   The

 to resolve tool invocation issues for other plugins.
    *   The

NEWSDATA_API_KEY

 was similarly set and applied.

3.  *Gateway Restarts:*
    *   The OpenClaw Gateway was restarted multiple times after configuration changes (plugin creation, file edits, dependency installs, directory moves) to ensure changes were loaded.

4.  *Testing:*
    *   Subagents were spawned to test

 was similarly set and applied.

3.  *Gateway Restarts:*
    *   The OpenClaw Gateway was restarted multiple times after configuration changes (plugin creation, file edits, dependency installs, directory moves) to ensure changes were loaded.

4.  *Testing:*
    *   Subagents were spawned to test

paper_trade_buy

and

and

get_portfolio_risk

.
    *   Both tools consistently failed with "tool not found" or "tool not available" errors.

*Observations:*

*   The

.
    *   Both tools consistently failed with "tool not found" or "tool not available" errors.

*Observations:*

*   The

market-data-plugin

 was set up using a very similar process and is working correctly.
*   The

 was set up using a very similar process and is working correctly.
*   The

execution-plugin

's

's

index.js

 uses the

 uses the

export default function(api)

 structure, and

 structure, and

api.registerTool

 is used with

 is used with

execute

 functions as per documentation.
*   The

 functions as per documentation.
*   The

in

in

openclaw.plugin.json

 was corrected to

 was corrected to

"execution-plugin"

 to match the directory and

 to match the directory and

openclaw.json

 entry.
*   The

 entry.
*   The

openclaw.json

 file explicitly enables

 file explicitly enables

"execution-plugin": { "enabled": true }

.

*Hypothesized Causes:*

*   A subtle difference in the

.

*Hypothesized Causes:*

*   A subtle difference in the

execution-plugin

's structure or files that OpenClaw's loader is sensitive to.
*   An issue with Node.js module resolution specifically for the

's structure or files that OpenClaw's loader is sensitive to.
*   An issue with Node.js module resolution specifically for the

execution-plugin

's dependencies or its

's dependencies or its

index.js

 file, despite

 file, despite

npm install

 completing.
*   A potential bug in OpenClaw's plugin loading mechanism that affects plugins named "execution" or those with similar structures to the

 completing.
*   A potential bug in OpenClaw's plugin loading mechanism that affects plugins named "execution" or those with similar structures to the

execution

 skill files.

We've exhausted standard troubleshooting steps for plugin creation and registration. The persistent failure of the

 skill files.

We've exhausted standard troubleshooting steps for plugin creation and registration. The persistent failure of the

execution-plugin

 while the

 while the

market-data-plugin` works flawlessly, despite similar setups, suggests a deeper issue.

Solution

To help others find answers, you can mark your question as solved via

Right click solution message -> Apps -> ✅ Mark Solution

Right click solution message -> Apps -> ✅ Mark Solution

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•3w ago•

26 replies

xJ577

Custom tools within Plugin not recognized

✅Solved

Problem:
The custom tools (

paper_trade_buy

paper_trade_buy

get_portfolio_risk

get_portfolio_risk

) within the

execution-plugin

execution-plugin

are not being recognized by OpenClaw. Despite following the plugin creation process successfully for the

market-data-plugin

market-data-plugin

(which now works), the

execution-plugin

execution-plugin

consistently fails with "tool not found" or "tool not available" errors.

Troubleshooting Steps Taken:

1. Initial Setup:
* Created plugin directory: .openclaw\extensions\execution-plugin


    *   Created


    *   Created

package.json

 with

 with

name

version

main: "index.js"

type: "module"

, and

, and

dependencies

node-fetch

).
    *   Created

).
    *   Created

openclaw.plugin.json

 manifest. Initially,

 manifest. Initially,

 was "execution", but later corrected to "execution-plugin" to match the directory name and

 was "execution", but later corrected to "execution-plugin" to match the directory name and

openclaw.json

 entry.
    *   Created

 entry.
    *   Created

index.js

 with the

 with the

export default function(api)

 structure and implemented

 structure and implemented

paper_trade_buy_execute

and

and

get_portfolio_risk_execute

 functions, registering them with

 functions, registering them with

api.registerTool

.
    *   Installed dependencies using

.
    *   Installed dependencies using

npm install --prefix

.
    *   Enabled the plugin in

.
    *   Enabled the plugin in

openclaw.json

plugins.entries["execution-plugin"].enabled = true

).
    *   Moved the plugin from

).
    *   Moved the plugin from

plugins

to

to

extensions

 directory.

2.  *API Key Configuration (for context, though not directly related to tool *recognition*):*
    *   The

 directory.

2.  *API Key Configuration (for context, though not directly related to tool *recognition*):*
    *   The

POLYGON_API_KEY

 was correctly set in

 was correctly set in

.openclaw/.env

 and applied via

 and applied via

gateway.config.patch

 and later direct edit to

 and later direct edit to

openclaw.json

 to resolve tool invocation issues for other plugins.
    *   The

 to resolve tool invocation issues for other plugins.
    *   The

NEWSDATA_API_KEY

 was similarly set and applied.

3.  *Gateway Restarts:*
    *   The OpenClaw Gateway was restarted multiple times after configuration changes (plugin creation, file edits, dependency installs, directory moves) to ensure changes were loaded.

4.  *Testing:*
    *   Subagents were spawned to test

 was similarly set and applied.

3.  *Gateway Restarts:*
    *   The OpenClaw Gateway was restarted multiple times after configuration changes (plugin creation, file edits, dependency installs, directory moves) to ensure changes were loaded.

4.  *Testing:*
    *   Subagents were spawned to test

paper_trade_buy

and

and

get_portfolio_risk

.
    *   Both tools consistently failed with "tool not found" or "tool not available" errors.

*Observations:*

*   The

.
    *   Both tools consistently failed with "tool not found" or "tool not available" errors.

*Observations:*

*   The

market-data-plugin

 was set up using a very similar process and is working correctly.
*   The

 was set up using a very similar process and is working correctly.
*   The

execution-plugin

's

's

index.js

 uses the

 uses the

export default function(api)

 structure, and

 structure, and

api.registerTool

 is used with

 is used with

execute

 functions as per documentation.
*   The

 functions as per documentation.
*   The

in

in

openclaw.plugin.json

 was corrected to

 was corrected to

"execution-plugin"

 to match the directory and

 to match the directory and

openclaw.json

 entry.
*   The

 entry.
*   The

openclaw.json

 file explicitly enables

 file explicitly enables

"execution-plugin": { "enabled": true }

.

*Hypothesized Causes:*

*   A subtle difference in the

.

*Hypothesized Causes:*

*   A subtle difference in the

execution-plugin

's structure or files that OpenClaw's loader is sensitive to.
*   An issue with Node.js module resolution specifically for the

's structure or files that OpenClaw's loader is sensitive to.
*   An issue with Node.js module resolution specifically for the

execution-plugin

's dependencies or its

's dependencies or its

index.js

 file, despite

 file, despite

npm install

 completing.
*   A potential bug in OpenClaw's plugin loading mechanism that affects plugins named "execution" or those with similar structures to the

 completing.
*   A potential bug in OpenClaw's plugin loading mechanism that affects plugins named "execution" or those with similar structures to the

execution

 skill files.

We've exhausted standard troubleshooting steps for plugin creation and registration. The persistent failure of the

 skill files.

We've exhausted standard troubleshooting steps for plugin creation and registration. The persistent failure of the

execution-plugin

 while the

 while the

market-data-plugin` works flawlessly, despite similar setups, suggests a deeper issue.

Solution

To help others find answers, you can mark your question as solved via

Right click solution message -> Apps -> ✅ Mark Solution

Right click solution message -> Apps -> ✅ Mark Solution

Jump to solution

Custom tools within Plugin not recognized

Custom tools within Plugin not recognized

Similar Threads

Similar Threads

Similar Threads