Get Started

Configure Tools Without Friction

This guide shows how to set tool type, method, handler, and schemas so your workflow runs reliably from the start.

Updated: April 16, 2026

Decision at a glance

  • File Resource Handler: list, read, and write files
  • Script Tool Handler: run JavaScript from the editor
  • Custom Tool Handler: integrate native plugins

Quick links

Quick Start Tool Types Schemas Common Errors Next Steps

Quick start in 5 steps

  1. Select the tool type that matches your use case.
  2. Set the method name (file operation or Custom Tool).
  3. Assign a clear, unique handler name.
  4. Define input and output schemas.
  5. Save and test with sample data.

Tool types and method names

File Resource Handler

Use this for file system actions such as List files, Read file, and Write file.

Script Tool Handler

Executes JavaScript from the editor. The central entry function is toolEntry.

Custom Tool Handler

Integrates native plugins. The method is typically Custom Tool.

Keep input and output schemas simple

Start with a small, clear schema and extend it only when needed.

{
  "type": "object",
  "properties": {
    "project_path": { "type": "string" },
    "pattern": { "type": "string" }
  },
  "required": ["project_path"]
}

A good output schema includes success data and a clear error field.

Common configuration mistakes

  • Wrong tool type: method is unavailable or behavior is unexpected.
  • Unclear handler name: difficult to maintain and debug later.
  • Schema too strict or too loose: unnecessary validation failures or unstable output.
Important: When changing a schema, also update prompt and script logic so all layers stay aligned.

Next steps