An AI agent is a module that receives data, context, and resources, then uses an AI model for reasoning, planning, and decision-making to achieve specific goals.
The GenAI Data Fusion framework includes two categories of agents, both represented as Broadway actors and flows.
| Agent | Role |
| Data Retrieve | Explores Fabric Data Products by generating SQL dynamically |
The implementation agents act as worker sub-agents in the agentic workflow, with the aim of accomplishing domain-specific goals. These are Broadway flows tagged to handle specific domains or request types.
Example: The loans_subagent tag identifies an agent specialized in banking loan inquiries.
Read more practice information here about the agentic workflow's built-in agents and worker sub-agents.
Tools are Broadway flows designed to perform specific actions.
While the generic Data Retrieve agent handles most queries using schema descriptions, tools become essential for:
Tools are identified by:
This information is passed to the LLM to aid in tool selection during plan execution.
While there are several built-in tools like queryExecute, tools are usually built as part of the project Implementation.
It is recommended to build tools at the data products. At your agentic flow you shall specify these tools, where AI Fusion agentic flow can call them either directly - as Broadway flow - from aifusion or from the relevant the data product, or as MCP.
Read here for more information about tools calling and consumption, according to tool tags naming conventions.
Note: Tools typically do not involve AI unless an agent is tagged as a tool.
The AI Fusion platform uses several utility actors for working with AI, such as LLMConst, LLAppend and LLInvoke.
For more information, read here.
An AI agent is a module that receives data, context, and resources, then uses an AI model for reasoning, planning, and decision-making to achieve specific goals.
The GenAI Data Fusion framework includes two categories of agents, both represented as Broadway actors and flows.
| Agent | Role |
| Data Retrieve | Explores Fabric Data Products by generating SQL dynamically |
The implementation agents act as worker sub-agents in the agentic workflow, with the aim of accomplishing domain-specific goals. These are Broadway flows tagged to handle specific domains or request types.
Example: The loans_subagent tag identifies an agent specialized in banking loan inquiries.
Read more practice information here about the agentic workflow's built-in agents and worker sub-agents.
Tools are Broadway flows designed to perform specific actions.
While the generic Data Retrieve agent handles most queries using schema descriptions, tools become essential for:
Tools are identified by:
This information is passed to the LLM to aid in tool selection during plan execution.
While there are several built-in tools like queryExecute, tools are usually built as part of the project Implementation.
It is recommended to build tools at the data products. At your agentic flow you shall specify these tools, where AI Fusion agentic flow can call them either directly - as Broadway flow - from aifusion or from the relevant the data product, or as MCP.
Read here for more information about tools calling and consumption, according to tool tags naming conventions.
Note: Tools typically do not involve AI unless an agent is tagged as a tool.
The AI Fusion platform uses several utility actors for working with AI, such as LLMConst, LLAppend and LLInvoke.
For more information, read here.