You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor(tools): rename meta tools to utility tools with tool_* prefix [ENG-11958] (#310)
* refactor(tools): rename meta tools to utility tools with tool_* prefix
Rename tool naming convention to avoid confusion with Facebook's Meta
brand. The "meta_*" prefix was ambiguous and could be misinterpreted.
File renames:
- examples/meta-tools.ts -> examples/utility-tools.ts
Tool name changes:
- meta_search_tools -> tool_search
- meta_execute_tool -> tool_execute
- meta_collect_tool_feedback -> tool_feedback
API changes:
- Tools.metaTools() -> Tools.utilityTools()
Internal type renames:
- MetaToolSearchResult -> ToolSearchResult
All tests pass (220 passed) and linting passes.
* Update src/tool.test.ts
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* fix(tests): update test descriptions from 'meta tools' to 'utility tools'
Address PR review comments to make test descriptions consistent with
the refactoring to use 'utility tools' terminology throughout:
- Update comment for mock tools creation function
- Fix 4 test descriptions that still referenced 'meta tools'
---------
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Copy file name to clipboardExpand all lines: README.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -355,18 +355,18 @@ This is especially useful when you want to:
355
355
356
356
[View full example](examples/fetch-tools.ts)
357
357
358
-
### Meta Tools (Beta)
358
+
### Utility Tools (Beta)
359
359
360
-
Meta tools enable dynamic tool discovery and execution, allowing AI agents to search for relevant tools based on natural language queries without hardcoding tool names.
360
+
Utility tools enable dynamic tool discovery and execution, allowing AI agents to search for relevant tools based on natural language queries without hardcoding tool names.
361
361
362
-
> **Beta Feature**: Meta tools are currently in beta and the API may change in future versions.
362
+
> **Beta Feature**: Utility tools are currently in beta and the API may change in future versions.
363
363
364
-
#### How Meta Tools Work
364
+
#### How Utility Tools Work
365
365
366
-
Meta tools provide two core capabilities:
366
+
Utility tools provide two core capabilities:
367
367
368
-
1.**Tool Discovery** (`meta_search_tools`): Search for tools using natural language queries
@@ -425,7 +425,7 @@ const result = await executeTool.execute({
425
425
});
426
426
```
427
427
428
-
[View full example](examples/meta-tools.ts)
428
+
[View full example](examples/utility-tools.ts)
429
429
430
430
### Custom Base URL
431
431
@@ -473,7 +473,7 @@ The `dryRun` option returns an object containing:
473
473
474
474
### Feedback Collection Tool
475
475
476
-
The StackOne AI SDK includes a built-in feedback collection tool (`meta_collect_tool_feedback`) that allows users to provide feedback on their experience with StackOne tools. This tool is automatically included when using `fetchTools()` and helps improve the SDK based on user input.
476
+
The StackOne AI SDK includes a built-in feedback collection tool (`tool_feedback`) that allows users to provide feedback on their experience with StackOne tools. This tool is automatically included when using `fetchTools()` and helps improve the SDK based on user input.
477
477
478
478
#### How It Works
479
479
@@ -498,7 +498,7 @@ const toolset = new StackOneToolSet({
Copy file name to clipboardExpand all lines: src/feedback.ts
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ export function createFeedbackTool(
47
47
accountId,
48
48
baseUrl,
49
49
};
50
-
constname='meta_collect_tool_feedback'asconst;
50
+
constname='tool_feedback'asconst;
51
51
constdescription=
52
52
'Collects user feedback on StackOne tool performance. First ask the user, "Are you ok with sending feedback to StackOne?" and mention that the LLM will take care of sending it. Call this tool only when the user explicitly answers yes.';
0 commit comments