Tools

Tools are the reusable actions your agents and workflows can call to get things done, like fetching live data, updating a record, or triggering an external service. Build a tool once, then equip any agent with it.

Think of a tool as a single capability you hand to an agent. You describe what it does and when to use it, connect it to the right data source, and the agent decides when to reach for it mid-conversation. RedFlare equips agents with real-time tools so they can process data and complete complex tasks instantly, without you scripting every step.

What you can do

• Create reusable tools that group and organize your agent's capabilities.
• Build Webhook tools that call your backend APIs to fetch or update real data while a conversation is in progress.
• Set up Client Tool actions that interact with the browser interface live.
• Keep simple Static tools that return a fixed, pre-written response.
• Define Dynamic Params so an agent can pull values like names, dates, or IDs straight from what the user says.
• Shape a Tool Response to control what the agent sees back after the tool runs.
• See at a glance how each tool is performing, including latency and API Usage.
• Track which agents and webhooks a tool is connected to before you change or remove it.
• Search, edit, and delete tools as your setup evolves.

How it works

A tool is a contract between your agent and an action. You give it a clear Name and Description, and that description is the single most important thing you write: the agent reads it to decide, in the middle of a live conversation, whether this tool is the right one to call right now.

Here is what happens behind the scenes once a tool is in play:

1. The agent recognizes a moment to act. As the conversation unfolds, the agent matches what the user is asking against your tool descriptions and picks the tool whose purpose fits.
2. It gathers the inputs. For each Dynamic Param you defined, the agent extracts the value from the conversation, such as a customer name, an order ID, or a date, and casts it to the type you specified (String, Number, or Boolean).
3. The request goes out. If the tool is a Webhook, RedFlare assembles the call to your API using the connected webhook's method and address, slotting the dynamic values into the headers, query parameters, path, or body where you mapped them. Values you fixed ahead of time are sent as-is; values marked dynamic are filled in live.
4. Your service responds. RedFlare receives the result from your API. The Tool Response you configured shapes what is handed back to the agent, so it gets a clean, predictable answer rather than a raw payload.
5. The agent continues. It folds the result into the conversation, answering the user or moving to the next step.

The tool's type is decided automatically by how you build it. Attach one or more webhooks and it becomes a Webhook tool; leave the webhooks off and it stays a Static tool that returns your fixed response. Client Tools are a separate type that acts on the browser interface in real time rather than calling an external service. Every call is measured, so the list view can show you how many times a tool ran, how often it succeeded, and how fast it responded.

Create a tool

When you open Tools for the first time, you'll see No tools created yet with a prompt to group and organize your agent's capabilities.

1. Select Create Tool (top right, or from the empty state).
2. In the Configuration panel, enter a Name for your tool.
3. Add a Description. This is where you give the agent clear guidance on what the tool does and the conditions under which it should be used.
4. Optionally fill in a Tool Response to shape what comes back after the tool runs.
5. Connect a webhook and add any parameters (see below).
6. Select Create to save. To discard, select Cancel.

While the tool saves, you'll see Tool creation in progress. Please wait. until it lands in your list.

tip

A precise description is what makes a tool reliable. Spell out exactly when the agent should reach for it, so it fires at the right moments and stays quiet otherwise. Vague descriptions lead to tools that fire too often or never at all.

Connect a webhook

Webhooks let a tool call your backend APIs so it can act on real data instead of returning something static.

1. Inside the create form, find the Webhooks section. If nothing is connected yet, you'll see No webhooks added yet.
2. Select Add webhooks to open the picker.
3. Search for the webhook you want and select it to attach it to the tool.
4. Don't have one yet? Select the option to create a new webhook without leaving the flow, then come back and add it.

You can attach more than one webhook to a single tool, and remove any you no longer need. The moment a webhook is attached, the tool's badge changes from Static to Webhooks.

note

A webhook carries its own request setup, including the method, address, headers, query parameters, path parameters, and body. Each value in that setup is either fixed or marked Dynamic. Dynamic values are the ones the agent fills in live from the conversation.

note

If every available webhook is already attached, you'll see Nothing left to add — all tools are already included. That just means there's nothing more to pick from.

Add dynamic parameters

Dynamic params are the values an agent extracts from the conversation and passes into the request at runtime, such as a user name, a date, or a specific ID. They are how a single tool handles endless variations of the same request.

1. In the Dynamic Params section, select Add.
2. Enter a Name for the parameter. This should match the value your webhook expects.
3. Choose a Data Type: String, Number, or Boolean.
4. Add a Description so the agent knows what to capture and when.
5. Repeat for each value you need, and remove any with the delete icon on the row.

When a webhook already has fields marked Dynamic, RedFlare can carry those across as parameters for you, so you aren't redefining the same values twice.

tip

Write parameter descriptions the same way you write the tool description: concretely. "The customer's six-digit order number" beats "order id" every time, because the agent uses your words to find the right value in the dialogue.

Edit or delete a tool

Each tool in the list shows its type (a Webhooks or Static badge), how many agents use it, and recent performance like latency and API Usage.

1. Select a tool to open it, or use the menu on its row.
2. Choose Edit to update its configuration, or Delete to remove it.
3. On delete, confirm by typing the tool's name.

If a tool is still in use, you'll see This tool is currently in use with the message Active connections detected. RedFlare lists the connected agents and webhooks and asks you to unlink the tool from them first, so you don't break anything that's live. Use Unlink Tool on each connection, then delete.

note

Changes save in the background. You may briefly see Tool update in progress. Please wait. or Tool unlink in progress. Please wait. while RedFlare applies the change.

Tips

tip

Use the search bar at the top of Tools to find a tool fast, and the refresh button to pull in the latest performance figures after a busy run.

tip

Read the success rate alongside latency. A tool that runs often but succeeds rarely usually points to a webhook problem, like a changed endpoint or a missing parameter, rather than the agent choosing it incorrectly.

note

Reuse beats duplication. Because tools are shared, one well-described tool connected to many agents is easier to maintain than near-identical copies. Before building a new one, search to see if an existing tool already covers the job.