You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The numerical score on a Likert scale (integer 1 to 5) and a higher score is better. Given a numerical threshold (default to 3), we also output "pass" if the score >= threshold, or "fail" otherwise. Using the reason and additional fields can help you understand why the score is high or low.
86
+
The numerical score is on a Likert scale (integer 1 to 5) and a higher score is better. Given a numerical threshold (default to 3), we also output "pass" if the score >= threshold, or "fail" otherwise. Using the reason and additional fields can help you understand why the score is high or low.
87
87
88
88
```python
89
89
{
@@ -104,14 +104,17 @@ The numerical score on a Likert scale (integer 1 to 5) and a higher score is bet
104
104
105
105
```
106
106
107
-
If you're building agents outside of Azure AI Agent Serice, this evaluator accepts a schema typical for agent messages. To learn more, see our sample notebook for [Intent Resolution](https://aka.ms/intentresolution-sample).
107
+
If you're building agents outside of Azure AI Agent Service, this evaluator accepts a schema typical for agent messages. To learn more, see our sample notebook for [Intent Resolution](https://aka.ms/intentresolution-sample).
108
108
109
109
## Tool call accuracy
110
110
111
-
`ToolCallAccuracyEvaluator` measures an agent's ability to select appropriate tools, extract, and process correct parameters from previous steps of the agentic workflow. It detects whether each tool call made is accurate (binary) and reports back the average scores, which can be interpreted as a passing rate across tool calls made.
111
+
`ToolCallAccuracyEvaluator` measures the accuracy and efficiency of tool calls made by an agent in a run. It provides a 1-5 score based on:
112
+
- the relevance and helpfulness of the tool invoked;
113
+
- the correctness of parameters used in tool calls;
114
+
- the counts of missing or excessive calls.
112
115
113
116
> [!NOTE]
114
-
> `ToolCallAccuracyEvaluator` only supports Azure AI Agent's Function Tool evaluation, but doesn't support Built-in Tool evaluation. The agent messages must have at least one Function Tool actually called to be evaluated.
117
+
> `ToolCallAccuracyEvaluator` only supports Azure AI Agent's Function Tool evaluation, but doesn't support Built-in Tool evaluation. The agent run must have at least one Function Tool call and no Built-in Tool calls made to be evaluated.
115
118
116
119
### Tool call accuracy example
117
120
@@ -150,20 +153,35 @@ tool_call_accuracy(
150
153
151
154
### Tool call accuracy output
152
155
153
-
The numerical score (passing rate of correct tool calls) is 0-1 and a higher score is better. Given a numerical threshold (default to 3), we also output "pass" if the score >= threshold, or "fail" otherwise. Using the reason and tool call detail fields can help you understand why the score is high or low.
156
+
The numerical score is on a Likert scale (integer 1 to 5) and a higher score is better. Given a numerical threshold (default to 3), we also output "pass" if the score >= threshold, or "fail" otherwise. Using the reason and tool call detail fields can help you understand why the score is high or low.
154
157
155
158
```python
156
159
{
157
-
"tool_call_accuracy": 1.0,
160
+
"tool_call_accuracy": 5,
158
161
"tool_call_accuracy_result": "pass",
159
-
"tool_call_accuracy_threshold": 0.8,
160
-
"per_tool_call_details": [
161
-
{
162
-
"tool_call_accurate": True,
163
-
"tool_call_accurate_reason": "The input Data should get a Score of 1 because the TOOL CALL is directly relevant to the user's question about the weather in Seattle, includes appropriate parameters that match the TOOL DEFINITION, and the parameter values are correct and relevant to the user's query.",
164
-
"tool_call_id": "call_CUdbkBfvVBla2YP3p24uhElJ"
162
+
"tool_call_accuracy_threshold": 3,
163
+
"details": {
164
+
"tool_calls_made_by_agent": 1,
165
+
"correct_tool_calls_made_by_agent": 1,
166
+
"per_tool_call_details": [
167
+
{
168
+
"tool_name": "fetch_weather",
169
+
"total_calls_required": 1,
170
+
"correct_calls_made_by_agent": 1,
171
+
"correct_tool_percentage": 1.0,
172
+
"tool_call_errors": 0,
173
+
"tool_success_result": "pass"
174
+
}
175
+
],
176
+
"excess_tool_calls": {
177
+
"total": 0,
178
+
"details": []
179
+
},
180
+
"missing_tool_calls": {
181
+
"total": 0,
182
+
"details": []
165
183
}
166
-
]
184
+
}
167
185
}
168
186
```
169
187
@@ -187,7 +205,7 @@ task_adherence(
187
205
188
206
### Task adherence output
189
207
190
-
The numerical score on a Likert scale (integer 1 to 5) and a higher score is better. Given a numerical threshold (default to 3), we also output "pass" if the score >= threshold, or "fail" otherwise. Using the reason field can help you understand why the score is high or low.
208
+
The numerical score is on a Likert scale (integer 1 to 5) and a higher score is better. Given a numerical threshold (default to 3), we also output "pass" if the score >= threshold, or "fail" otherwise. Using the reason field can help you understand why the score is high or low.
Copy file name to clipboardExpand all lines: articles/ai-foundry/concepts/resource-types.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.reviewer: deeikele
7
7
manager: scottpolly
8
8
author: sgilley
9
9
ms.author: sgilley
10
-
ms.date: 05/18/2025
10
+
ms.date: 07/22/2025
11
11
ms.service: azure-ai-foundry
12
12
ms.topic: concept-article
13
13
ms.custom:
@@ -19,15 +19,15 @@ ms.custom:
19
19
20
20
An Azure resource is required to use and manage services in Azure. It defines the scope for configuring, securing, and monitoring the tools or capabilities you want to use—like AI models, agents, or storage.
21
21
22
-
AI Foundry Portal and SDK clients support multiple distinct Azure resource types, each designed to serve different development and operational needs. This article explains which use case requires which type.
22
+
Azure AI Foundry portal and SDK clients support multiple distinct Azure resource types, each designed to serve different development and operational needs. This article explains which use case requires which type.
23
23
24
24
## Resource Types supported with AI Foundry
25
25
26
-
***Azure AI Foundry** – The primary resource type for designing, deploying, and managing generative AI applications and agents. It provides access to agent service, models that are hosted using a serverless hosting model, evaluations, and Azure OpenAI service. This is the recommended resource type for most applications built in Azure AI Foundry.
26
+
***Azure AI Foundry** – The primary resource type for designing, deploying, and managing generative AI applications and agents. It provides access to agent service, models that are hosted using a serverless hosting model, evaluations, and Azure OpenAI service. Azure AI Foundry is the recommended resource type for most applications built in Azure AI Foundry.
27
27
28
28
Get started by [creating a first AI Foundry resource](../../ai-services/multi-service-resource.md?context=/azure/ai-foundry/context/context).
29
29
30
-
***Azure AI Hub** – Use this resource type in combination with Azure AI Foundry to additionally access open-source model hosting and fine-tuning capabilities, as well as Azure Machine Learning capabilities. When you create an AI Hub, an Azure AI Foundry resource is automatically provisioned. Hub resources can be used in both AI Foundry Portal and Machine Learning Studio.
30
+
***Azure AI Hub** – Use this resource type in combination with Azure AI Foundry to additionally access open-source model hosting and fine-tuning capabilities, as well as Azure Machine Learning capabilities. When you create an AI Hub, an Azure AI Foundry resource is automatically provisioned. Hub resources can be used in both Azure AI Foundry portal and Machine Learning Studio.
31
31
32
32
***Azure AI Search** – A resource used to index and retrieve data for grounding AI applications. It can be [connected](../how-to/connections-add.md) to Azure AI Foundry agents to enable retrieval-augmented generation (RAG) and semantic search experiences.
Use a [Microsoft Bicep](/azure/azure-resource-manager/bicep/overview) file (template) to create an [Azure AI Foundry](https://ai.azure.com/?cid=learnDocs) resource. A template makes it easy to create resources as a single, coordinated operation. A Bicep file is a text document that defines the resources that are needed for a deployment. It might also specify deployment parameters. Parameters are used to provide input values when using the file to deploy resources.
24
22
25
23
## Prerequisites
@@ -64,14 +62,14 @@ Deploy the Bicep file using either the Azure CLI or Azure PowerShell.
64
62
65
63
```azurecli
66
64
az group create --name exampleRG --location eastus
67
-
az deployment group create --resource-group exampleRG --template-file main.bicep --parameters aiServicesName=myai aiProjectName=myai-proj
65
+
az deployment group create --resource-group exampleRG --template-file main.bicep --parameters aiFoundryName=myai aiProjectName=myai-proj
0 commit comments