> For the complete documentation index, see [llms.txt](https://docs.contextual.io/documentation-and-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.contextual.io/documentation-and-resources/components-and-data/flows/node-reference/ai-gateway/ai-tool-response.md).
# AI Tool Response
Return a response for a tool invocation that started from an AI Tool node.
## Where to Find It
In the Flow Editor, in the left palette look under **AI Gateway**, then drag **Tool Response** onto your canvas.
AI Tool Response configuration with the Output property.
## What It Does
The Tool Response node sends the tool result back to the original AI Generate request so the model can continue with the returned data.
## Configuration
1. **Name** (optional) - Provide a friendly label for the node.
2. **Output** (required) - The property containing the tool result.
* Use a `msg` reference (default: `msg.payload`) to return a computed result.
* Use a static string when you want to return a fixed response.
## Outputs
* Strings are returned directly.
* Objects are stringified before being returned to the model.
Use this node at the end of a tool execution path so the model receives the tool output.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.contextual.io/documentation-and-resources/components-and-data/flows/node-reference/ai-gateway/ai-tool-response.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
