github/penpot-mcp
1
0
Fork 0
mirror of https://github.com/penpot/penpot-mcp.git synced 2026-04-25 11:18:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

Improve description of ExecuteCodeTool

Browse Source
This commit is contained in:
Dominik Jain 2025-10-19 23:03:22 +02:00
parent 670b0d6b07
commit ef060c4da6
1 changed files with 11 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
mcp-server/src/tools/ExecuteCodeTool.ts
View File

@ -46,13 +46,17 @@ export class ExecuteCodeTool extends Tool<ExecuteCodeArgs> {
"Executes JavaScript code in the Penpot plugin context.\n" + "Executes JavaScript code in the Penpot plugin context.\n" +
"IMPORTANT: Before using this tool, make sure you have read the 'Penpot High-Level Overview' and know " + "IMPORTANT: Before using this tool, make sure you have read the 'Penpot High-Level Overview' and know " +
"which Penpot API functionality is necessary and how to use it.\n" + "which Penpot API functionality is necessary and how to use it.\n" +
"You have access two main objects: `penpot` (the Penpot API, of type `Penpot`) and `storage` (an object in which arbitrary " + "You have access two main objects: `penpot` (the Penpot API, of type `Penpot`), `penpotUtils`, " +
"data can be stored, simply by adding a new attribute; stored attributes can be referenced in future calls " + "and `storage`.\n" +
"to this tool, so any intermediate results that could come in handy later should be stored in `storage` " + "`storage` is an object in which arbitrary data can be stored, simply by adding a new attribute; " +
"instead of just a fleeting variable).\n" + "stored attributes can be referenced in future calls to this tool, so any intermediate results that " +
"The tool call returns the value of the concluding `return` statement, if any.\n" + "could come in handy later should be stored in `storage` instead of just a fleeting variable; " +
"Any output that you generate via the `console` object will be returned to you; so you may use this" + "you can also store functions and thus build up a library).\n" +
"to track what your code is doing, but you should only do so only if there is an ACTUAL NEED for this! " + "Think of the code being executed as the body of a function: " +
"The tool call returns whatever you return in the applicable `return` statement, if any.\n" +
"If an exception occurs, the exception's message will be returned to you.\n" +
"Any output that you generate via the `console` object will be returned to you separately; so you may use it" +
"to track what your code is doing, but you should *only* do so only if there is an ACTUAL NEED for this! " +
"VERY IMPORTANT: Don't use logging prematurely! NEVER log the data you are returning, as you will otherwise receive it twice!\n" + "VERY IMPORTANT: Don't use logging prematurely! NEVER log the data you are returning, as you will otherwise receive it twice!\n" +
"VERY IMPORTANT: In general, try a simple approach first, and only if it fails, try more complex code that involves " + "VERY IMPORTANT: In general, try a simple approach first, and only if it fails, try more complex code that involves " +
"handling different cases (in particular error cases) and that applies logging." "handling different cases (in particular error cases) and that applies logging."