@quilltap/plugin-types 1.7.0 → 1.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -5,6 +5,16 @@ All notable changes to this project will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [1.8.0] - 2026-01-13
9
+
10
+ ### Added
11
+
12
+ - Multi-tool plugin support for `ToolPlugin` interface:
13
+ - `getMultipleToolDefinitions?: () => UniversalTool[]` - Allows plugins to provide multiple tools dynamically
14
+ - `executeByName?: (toolName, input, context) => Promise<ToolExecutionResult>` - Execute a specific tool by name (required for multi-tool plugins)
15
+ - `onConfigurationChange?: (config) => Promise<void>` - Callback when user configuration changes
16
+ - These additions enable plugins like the MCP connector to discover and expose multiple tools from external servers
17
+
8
18
  ## [1.7.0] - 2026-01-09
9
19
 
10
20
  ### Added
package/dist/index.d.mts CHANGED
@@ -175,6 +175,37 @@ interface ToolPlugin {
175
175
  renderIcon?: (props: {
176
176
  className?: string;
177
177
  }) => React.ReactNode;
178
+ /**
179
+ * Get multiple tool definitions (optional)
180
+ *
181
+ * For plugins that provide multiple tools dynamically (e.g., MCP connector).
182
+ * When implemented, the registry will call this instead of getToolDefinition()
183
+ * and register each returned tool separately.
184
+ *
185
+ * @returns Array of tool definitions in universal format
186
+ */
187
+ getMultipleToolDefinitions?: () => UniversalTool[];
188
+ /**
189
+ * Execute a specific tool by name (optional)
190
+ *
191
+ * Required when getMultipleToolDefinitions is implemented.
192
+ * The registry routes execution to this method based on the tool name.
193
+ *
194
+ * @param toolName The name of the tool to execute (as returned by getMultipleToolDefinitions)
195
+ * @param input The input arguments from the LLM
196
+ * @param context Execution context with user/chat info and config
197
+ * @returns Promise resolving to the execution result
198
+ */
199
+ executeByName?: (toolName: string, input: Record<string, unknown>, context: ToolExecutionContext) => Promise<ToolExecutionResult>;
200
+ /**
201
+ * Called when configuration changes (optional)
202
+ *
203
+ * Allows plugins to refresh their state when user configuration changes.
204
+ * For multi-tool plugins, this may trigger re-discovery of available tools.
205
+ *
206
+ * @param config The updated user configuration
207
+ */
208
+ onConfigurationChange?: (config: Record<string, unknown>) => Promise<void>;
178
209
  }
179
210
  /**
180
211
  * Standard export type for tool plugins
package/dist/index.d.ts CHANGED
@@ -175,6 +175,37 @@ interface ToolPlugin {
175
175
  renderIcon?: (props: {
176
176
  className?: string;
177
177
  }) => React.ReactNode;
178
+ /**
179
+ * Get multiple tool definitions (optional)
180
+ *
181
+ * For plugins that provide multiple tools dynamically (e.g., MCP connector).
182
+ * When implemented, the registry will call this instead of getToolDefinition()
183
+ * and register each returned tool separately.
184
+ *
185
+ * @returns Array of tool definitions in universal format
186
+ */
187
+ getMultipleToolDefinitions?: () => UniversalTool[];
188
+ /**
189
+ * Execute a specific tool by name (optional)
190
+ *
191
+ * Required when getMultipleToolDefinitions is implemented.
192
+ * The registry routes execution to this method based on the tool name.
193
+ *
194
+ * @param toolName The name of the tool to execute (as returned by getMultipleToolDefinitions)
195
+ * @param input The input arguments from the LLM
196
+ * @param context Execution context with user/chat info and config
197
+ * @returns Promise resolving to the execution result
198
+ */
199
+ executeByName?: (toolName: string, input: Record<string, unknown>, context: ToolExecutionContext) => Promise<ToolExecutionResult>;
200
+ /**
201
+ * Called when configuration changes (optional)
202
+ *
203
+ * Allows plugins to refresh their state when user configuration changes.
204
+ * For multi-tool plugins, this may trigger re-discovery of available tools.
205
+ *
206
+ * @param config The updated user configuration
207
+ */
208
+ onConfigurationChange?: (config: Record<string, unknown>) => Promise<void>;
178
209
  }
179
210
  /**
180
211
  * Standard export type for tool plugins
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@quilltap/plugin-types",
3
- "version": "1.7.0",
3
+ "version": "1.8.0",
4
4
  "description": "Type definitions for Quilltap plugin development",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",