jyapayne/langflow
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

docs: langflow docs review (#8032)

Browse source 
* quickstart

* message-history

* concepts-components

* data

* helpers

* logic-and-memories

* models

* agent-descriptions

* langsmith-more-env-vars

* use-kbd

* modify-descriptions

* Apply suggestions from code review

Co-authored-by: KimberlyFields <46325568+KimberlyFields@users.noreply.github.com>
Co-authored-by: Victor-w-Madeira <victor.wmadeira@gmail.com>

* remove-duplicate-periods

* remove-str-no-longer-used-in-ports

---------

Co-authored-by: KimberlyFields <46325568+KimberlyFields@users.noreply.github.com>
Co-authored-by: Victor-w-Madeira <victor.wmadeira@gmail.com>
This commit is contained in:
Mendon Kissling 2025-05-15 13:55:14 -04:00 • committed by GitHub
commit 58bdabf5a3
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
10 changed files with 146 additions and 134 deletions
Download patch file Download diff file Expand all files Collapse all files

18
docs/docs/Agents/agent-tool-calling-agent-component.md
View file

@ -10,7 +10,7 @@ The `AgentComponent` is a component for easily creating an AI agent capable of a
The component contains all of the elements you'll need for creating an agent. Instead of managing LLM models and providers, pick your model and enter your API key. Instead of connecting a **Prompt** component, enter instructions in the component's **Agent Instruction** fields.
![Tool calling agentcomponent](/img/tool-calling-agent-component.png)
![Tool calling agent component](/img/tool-calling-agent-component.png)
Learn how to build a flow starting with the **Tool calling agent** component, and see how it can help you solve problems.
@ -19,7 +19,7 @@ Learn how to build a flow starting with the **Tool calling agent** component, an
- [An OpenAI API key](https://platform.openai.com/)
- [A Search API key](https://www.searchapi.io/)
## Create a problem-solving agent with AgentComponent
## Create a problem-solving agent with the Agent component
Create a problem-solving agent in Langflow, starting with the **Tool calling agent**.
@ -58,17 +58,17 @@ See what problems you can solve with this flow. As your problem becomes more spe
### Edit a tool's metadata
To edit a tool's metadata, click the **Edit Tools** button in the tool to modify its `name` or `description` metadata. These fields help connected agents understand how to use the tool, without having to modify the agent's prompt instructions.
To edit a tool's metadata, click the **Edit Tools** button in the tool to modify its `name`, `description`, or `enabled` metadata. These fields help connected agents understand how to use the tool, without having to modify the agent's prompt instructions.
For example, the [URL](/components-data#url) component has three tools available when **Tool Mode** is enabled.
| Tool Name | Description |
|-----------|-------------|
| `URL-fetch_content` | Use this tool to fetch and retrieve raw content from a URL, including HTML and other structured data. The full response content is returned. |
| `URL-fetch_content_text` | Use this tool to fetch and extract clean, readable text content from a webpage. Only plain text content is returned. |
| `URL-as_dataframe` | Use this tool to fetch structured data from a URL and convert it into a tabular format. Data is returned in a structured DataFrame table format. |
| Tool Name | Description | Enabled |
|-----------|-------------|---------|
| `URL-fetch_content` | Use this tool to fetch and retrieve raw content from a URL, including HTML and other structured data. The full response content is returned. | true |
| `URL-fetch_content_text` | Use this tool to fetch and extract clean, readable text content from a webpage. Only plain text content is returned. | true |
| `URL-as_dataframe` | Use this tool to fetch structured data from a URL and convert it into a tabular format. Data is returned in a structured DataFrame table format. | true |
A connected agent will have a clear idea of each tool's capabilities based on the `name` and `description` metadata. If you think the agent is using a tool incorrectly, edit a tool's metadata to help it understand the tool better.
A connected agent will have a clear idea of each tool's capabilities based on the `name` and `description` metadata. The `enabled` boolean controls the tool's availability to the agent. If you think an agent is using a tool incorrectly, edit a tool's metadata to help the agent better understand the tool.
Tool names and descriptions can be edited, but the default tool identifiers cannot be changed. If you want to change the tool identifier, create a custom component.