diff options
Diffstat (limited to 'docs/core')
| -rw-r--r-- | docs/core/tools-api.md | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/docs/core/tools-api.md b/docs/core/tools-api.md index 1ecc76e2..be19c760 100644 --- a/docs/core/tools-api.md +++ b/docs/core/tools-api.md @@ -67,7 +67,6 @@ Each of these tools extends `BaseTool` and implements the required methods for i While direct programmatic registration of new tools by users isn't explicitly detailed as a primary workflow in the provided files for typical end-users, the architecture supports extension through: - **Command-based Discovery:** Advanced users or project administrators can define a `toolDiscoveryCommand` in `settings.json`. This command, when run by the Gemini CLI core, should output a JSON array of `FunctionDeclaration` objects. The core will then make these available as `DiscoveredTool` instances. The corresponding `toolCallCommand` would then be responsible for actually executing these custom tools. - \ - **MCP Server(s):** For more complex scenarios, one or more MCP servers can be set up and configured via the `mcpServers` setting in `settings.json`. The Gemini CLI core can then discover and use tools exposed by these servers. As mentioned, if you have multiple MCP servers, the tool names will be prefixed with the server name from your configuration (e.g., `serverAlias__actualToolName`). This tool system provides a flexible and powerful way to augment the Gemini model\'s capabilities, making the Gemini CLI a versatile assistant for a wide range of tasks. |