From e84f1a5549f9cb1ff478401cd3588cc839dd7322 Mon Sep 17 00:00:00 2001 From: Reid <61492567+reidliu41@users.noreply.github.com> Date: Mon, 3 Mar 2025 00:13:17 +0800 Subject: [PATCH] fix: fix pre-commit check issue (#1349) # What does this PR do? [Provide a short summary of what this PR does and why. Link to relevant issues if applicable.] For https://github.com/meta-llama/llama-stack/actions/runs/13614599967/job/38056042207?pr=1348 ``` Fixing docs/source/building_applications/tools.md check for added large files..............................................Passed fix end of files.........................................................Passed Insert license in comments...............................................Passed ruff.....................................................................Passed ruff-format..............................................................Passed blacken-docs.............................................................Passed uv-lock..................................................................Passed uv-export................................................................Passed mypy.....................................................................Passed Distribution Template Codegen............................................Passed pre-commit hook(s) made changes. If you are seeing this message in CI, reproduce locally with: `pre-commit run --all-files`. To run `pre-commit` as part of git workflow, use `pre-commit install`. All changes made by hooks: diff --git a/docs/source/building_applications/tools.md b/docs/source/building_applications/tools.md index afffbc8..5a569ff 100644 --- a/docs/source/building_applications/tools.md +++ b/docs/source/building_applications/tools.md @@ -127,7 +127,7 @@ MCP tools require: ## Adding Custom Tools -When you want to use tools other than the built-in tools, you can implement a python function and decorate it with `@client_tool`. +When you want to use tools other than the built-in tools, you can implement a python function and decorate it with `@client_tool`. To define a custom tool, you need to use the `@client_tool` decorator. ```python Error: Process completed with exit code 1. ``` [//]: # (If resolving an issue, uncomment and update the line below) [//]: # (Closes #[issue-number]) ## Test Plan [Describe the tests you ran to verify your changes with result summaries. *Provide clear instructions so the plan can be easily re-executed.*] [//]: # (## Documentation) Signed-off-by: reidliu Co-authored-by: reidliu --- docs/source/building_applications/tools.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/building_applications/tools.md b/docs/source/building_applications/tools.md index afffbc8ce..5a569ff84 100644 --- a/docs/source/building_applications/tools.md +++ b/docs/source/building_applications/tools.md @@ -127,7 +127,7 @@ MCP tools require: ## Adding Custom Tools -When you want to use tools other than the built-in tools, you can implement a python function and decorate it with `@client_tool`. +When you want to use tools other than the built-in tools, you can implement a python function and decorate it with `@client_tool`. To define a custom tool, you need to use the `@client_tool` decorator. ```python