docs: fix navigation for passing run time values to tools

docs/docs/how-tos/index.md

@@ -25,7 +25,7 @@ Recipes showing how to apply common design patterns in your workflows:
 The following examples are useful especially if you are used to LangChain's AgentExecutor configurations.
 
 - [Force calling a tool first](force-calling-a-tool-first.ipynb): Define a fixed workflow before ceding control to the ReAct agent
-- [Passing run time values to tools](passing-run-time-values-to-tools): Pass values that are only known at run time to tools (e.g., the ID of the user who made the request)
+- [Passing run time values to tools](passing-run-time-values-to-tools.ipynb): Pass values that are only known at run time to tools (e.g., the ID of the user who made the request)
 - [Dynamic direct return](dynamically-returning-directly.ipynb): Let the LLM decide whether the graph should finish after a tool is run or whether the LLM should be able to review the output and keep going
 - [Respond in structured format](respond-in-format.ipynb): Let the LLM use tools or populate schema to provide the user. Useful if your agent should generate structured content
 - [Managing agent steps](managing-agent-steps.ipynb): How to format the intermediate steps of your workflow for the agent

docs/mkdocs.yml

@@ -147,6 +147,7 @@ nav:
          - "Map-reduce": how-tos/map-reduce.ipynb
          - "Human-in-the-Loop": how-tos/human-in-the-loop.ipynb
          - "Force Calling a Tool First": how-tos/force-calling-a-tool-first.ipynb
+         - "Passing Run-Time Values to Tools": how-tos/passing-run-time-values-to-tools.ipynb
          - "Dynamic Direct Return": how-tos/dynamically-returning-directly.ipynb
          - "Respond in Structured Format": how-tos/respond-in-format.ipynb
          - "Managing Agent Steps": how-tos/managing-agent-steps.ipynb