@toolforest/toolforest-plugin 0.3.2 → 0.3.3

package/dist/src/prompt.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"prompt.d.ts","sourceRoot":"","sources":["../../src/prompt.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,YAAY,CAAC;AAE9C;;;GAGG;AACH,wBAAgB,UAAU,CAAC,KAAK,EAAE,WAAW,GAAG,MAAM,CAiCrD"}
+{"version":3,"file":"prompt.d.ts","sourceRoot":"","sources":["../../src/prompt.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,YAAY,CAAC;AAE9C;;;GAGG;AACH,wBAAgB,UAAU,CAAC,KAAK,EAAE,WAAW,GAAG,MAAM,CAmCrD"}

package/dist/src/prompt.js

@@ -25,13 +25,15 @@ You have ${state.toolCount} Toolforest tools available, prefixed with "toolfores
 Connected toolkits:
 ${toolkitLines}
 
+Tool naming: tools follow the pattern toolforest_{toolkit}_{action} (e.g. toolforest_github_list_repos, toolforest_google_sheets_get_values).
+
 Rules:
 - Use Toolforest tools for tasks involving the connected services above.
 - Call tools directly by name — no discovery step needed.
 - Do NOT fabricate tool names not listed above.
 - Do NOT use pretrained knowledge about Toolforest APIs.
 - If a tool returns an auth error, direct the user to www.toolforest.io to reconnect.
-- Your API key is at plugins.entries.toolforest.config.apiKey in openclaw.json if needed.
+- If native tools are not working, use the /toolforest-mcp skill for curl-based fallback access.
 </toolforest>`;
 }
 //# sourceMappingURL=prompt.js.map

package/dist/src/prompt.js.map

@@ -1 +1 @@
-{"version":3,"file":"prompt.js","sourceRoot":"","sources":["../../src/prompt.ts"],"names":[],"mappings":"AAEA;;;GAGG;AACH,MAAM,UAAU,UAAU,CAAC,KAAkB;IAC3C,IAAI,KAAK,CAAC,MAAM,KAAK,OAAO,EAAE,CAAC;QAC7B,OAAO;+BACoB,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,WAAW,KAAK,CAAC,OAAO,EAAE,CAAC,CAAC,CAAC,EAAE;;;;;;;;;cAShE,CAAC;IACb,CAAC;IAED,MAAM,YAAY,GAAG,KAAK,CAAC,QAAQ;SAChC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,OAAO,CAAC,CAAC,IAAI,KAAK,CAAC,CAAC,WAAW,IAAI,kBAAkB,EAAE,CAAC;SACnE,IAAI,CAAC,IAAI,CAAC,CAAC;IAEd,OAAO;WACE,KAAK,CAAC,SAAS;;;EAGxB,YAAY;;;;;;;;;cASA,CAAC;AACf,CAAC"}
+{"version":3,"file":"prompt.js","sourceRoot":"","sources":["../../src/prompt.ts"],"names":[],"mappings":"AAEA;;;GAGG;AACH,MAAM,UAAU,UAAU,CAAC,KAAkB;IAC3C,IAAI,KAAK,CAAC,MAAM,KAAK,OAAO,EAAE,CAAC;QAC7B,OAAO;+BACoB,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,WAAW,KAAK,CAAC,OAAO,EAAE,CAAC,CAAC,CAAC,EAAE;;;;;;;;;cAShE,CAAC;IACb,CAAC;IAED,MAAM,YAAY,GAAG,KAAK,CAAC,QAAQ;SAChC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,OAAO,CAAC,CAAC,IAAI,KAAK,CAAC,CAAC,WAAW,IAAI,kBAAkB,EAAE,CAAC;SACnE,IAAI,CAAC,IAAI,CAAC,CAAC;IAEd,OAAO;WACE,KAAK,CAAC,SAAS;;;EAGxB,YAAY;;;;;;;;;;;cAWA,CAAC;AACf,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@toolforest/toolforest-plugin",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "description": "OpenClaw plugin for Toolforest — registers all connected tools as native agent tools",
   "type": "module",
   "main": "./dist/index.js",

package/skills/toolforest-mcp/SKILL.md

@@ -7,9 +7,11 @@ metadata:
 
 # Toolforest MCP Fallback
 
+Use this when Toolforest native tools (prefixed `toolforest_`) are not registered or not working.
+
 ## API Key
 
-First check the openclaw config:
+Check the openclaw config:
 ```bash
 grep -A5 '"toolforest"' ~/.openclaw/openclaw.json
 ```
@@ -22,7 +24,14 @@ https://mcp.toolforest.io/mcp
 Authorization: Bearer <apiKey>
 ```
 
-## Discover toolkits
+## Important: How Toolforest discovery works
+
+Toolforest uses **meta-tools** exposed via the standard MCP `tools/call` method. Do NOT use `tools/list` to discover toolkit tools — that only returns the 3 meta-tools (`list_tools`, `get_tool_schema`, `execute_tool`).
+
+Instead, use the meta-tools in this order:
+
+## Step 1: List connected toolkits
+
 ```bash
 curl -s -X POST https://mcp.toolforest.io/mcp \
   -H "Content-Type: application/json" \
@@ -30,15 +39,40 @@ curl -s -X POST https://mcp.toolforest.io/mcp \
   -d '{"jsonrpc":"2.0","id":"1","method":"tools/call","params":{"name":"list_tools","arguments":{}}}'
 ```
 
-## Execute a tool
+Returns an array of toolkit objects with `name` and `description` (e.g. `github`, `google_sheets`, `gmail`).
+
+## Step 2: List tools for a specific toolkit
+
+```bash
+curl -s -X POST https://mcp.toolforest.io/mcp \
+  -H "Content-Type: application/json" \
+  -H "Authorization: Bearer YOUR_KEY" \
+  -d '{"jsonrpc":"2.0","id":"1","method":"tools/call","params":{"name":"list_tools","arguments":{"toolkit":"github"}}}'
+```
+
+Returns tool descriptors with `name`, `summary`, `kind`, and `schema` for each tool in that toolkit.
+
+## Step 3: Get a tool's parameter schema (optional)
+
+```bash
+curl -s -X POST https://mcp.toolforest.io/mcp \
+  -H "Content-Type: application/json" \
+  -H "Authorization: Bearer YOUR_KEY" \
+  -d '{"jsonrpc":"2.0","id":"1","method":"tools/call","params":{"name":"get_tool_schema","arguments":{"tool_name":"github-list_repos"}}}'
+```
+
+## Step 4: Execute a tool
+
 ```bash
 curl -s -X POST https://mcp.toolforest.io/mcp \
   -H "Content-Type: application/json" \
   -H "Authorization: Bearer YOUR_KEY" \
   -d '{
     "jsonrpc": "2.0", "id": "1", "method": "tools/call",
-    "params": { "name": "execute_tool", "arguments": { "tool_name": "TOOL_NAME", "args": {} } }
+    "params": { "name": "execute_tool", "arguments": { "tool_name": "github-list_repos", "args": {"owner": "example"} } }
   }'
 ```
 
+Tool names follow the pattern `{toolkit}-{action}` (e.g. `github-list_repos`, `google_sheets-get_values`).
+
 Responses may be SSE (`data: {...}`) or plain JSON — handle both.