Goal Accuracy
The Goal Accuracy metric is a multi-turn agentic metric that evaluates your LLM agent's abilities on planning and executing the plan to finish a task or reach a goal. It is a self-explaining eval, which means it outputs a reason for its metric score.
Required Arguments
To use the GoalAccuracyMetric, you'll have to provide the following arguments when creating a ConversationalTestCase:
turns
You can learn more about how it is calculated here.
Usage
First, set the eval mode:
deepeval set-eval-mode llm # LLM-as-a-judge (default)
deepeval set-eval-mode hybrid # LLM extracts, Jev decides
deepeval set-eval-mode system_one # Jev-as-a-judge, no LLMThe GoalAccuracyMetric() can be used for end-to-end multi-turn evaluations of agents.
from deepeval.test_case import Turn, ConversationalTestCase, ToolCall
from deepeval.metrics import GoalAccuracyMetric
from deepeval import evaluate
convo_test_case = ConversationalTestCase(
turns=[
Turn(role="...", content="..."),
Turn(role="...", content="...", tools_called=[...])
],
)
metric = GoalAccuracyMetric(threshold=0.5)
# To run metric as a standalone
# metric.measure(convo_test_case)
# print(metric.score, metric.reason)
evaluate(test_cases=[convo_test_case], metrics=[metric])There are NINE optional parameters when creating a GoalAccuracyMetric:
- [Optional]
threshold: a number representing the minimum passing threshold. Can also be set toNoneto run the metric in score-only mode. Defaulted to0.5. - [Optional]
model: a string specifying which of OpenAI's GPT models to use, OR any custom LLM model of typeDeepEvalBaseLLM. Defaulted togpt-5.4. - [Optional]
include_reason: a boolean which when set toTrue, will include a reason for its evaluation score. Defaulted toTrue. - [Optional]
strict_mode: a boolean which when set toTrue, enforces a binary metric score: 1 for perfection, 0 otherwise. It also overrides the current threshold and sets it to 1. Defaulted toFalse. -
[Optional]
async_mode: a boolean which when set toTrue, enables concurrent execution within themeasure()method. Defaulted toTrue. - [Optional]
verbose_mode: a boolean which when set toTrue, prints the intermediate steps used to calculate said metric to the console, as outlined in the How Is It Calculated section. Defaulted toFalse. - [Optional]
flaky: a boolean which when set toTrue, marks the metric as flaky. Defaulted toFalse. - [Optional]
system_one_model: the Jev model to use, as a string or aDeepEvalBaseSystemOneModel. Only used underhybridorsystem_oneeval_mode. Defaulted tojev-latest. - [Optional]
eval_mode:llm,hybridorsystem_one, choosing whether an LLM, Jev, or both judge. Defaulted to the configured eval mode (llmunless set).
As a standalone
You can also run the GoalAccuracyMetric on a single test case as a standalone, one-off execution.
...
metric.measure(convo_test_case)
print(metric.score, metric.reason)How Is It Calculated
You can change how the GoalAccuracyMetric is calculated by setting the eval mode.
LLM-as-a-judge
The GoalAccuracyMetric score is calculated using the following steps:
- Find individual goals and steps taken by your LLM agent for each user-assistat interactions.
- Find goal accuracy scores for each of the goal-steps pairs using the evaluation model.
- Find plan quality and plan adherence scores for each of the goal-step pairs using the evaluation model.
Hybrid
Under the hybrid eval mode, the goal accuracy and plan quality of each interaction are rated by Jev, a System One model, on a five-level scale mapped onto 0 to 1. Each interaction's reason states Jev's score and confidence, and the LLM writes the final reason. If a Jev call fails, the LLM makes that decision instead.
Jev-as-a-judge
Under the system_one eval mode, Jev judges the whole metric in one request. It is sent the whole conversation (with the tools called in each turn) and asked three questions:
| Question | Type | Weight |
|---|---|---|
Every goal the user states in turns is fully and correctly achieved in the assistant turns that follow it, as seen by the user. | Noul | 2 |
Across turns, how fully and correctly do the assistant's visible replies achieve the goals the user states? (Not achieved → Fully achieved) | Score | 1 |
Across turns, how clear and complete is the assistant's plan (including its tools_called) for each user goal, and how closely does it follow that plan? (No plan → Complete plan, fully followed) | Score | 1 |
Each answer becomes a value in and the score is their weighted mean. No LLM is called: the reason lists each answer with its probability, and metric.confidence reports how decisive Jev was.
FAQs
My agent answered every message but still failed the user's actual goal — will this catch it?
GoalAccuracyMetric extracts the underlying task from the user's messages and judges whether the agent's plan and steps actually reached it. A conversation can look responsive turn by turn yet score low if the goal was never accomplished.What's the difference between the goal score and the plan score?
How does it know the goal if I never pass an expected outcome?
"user" messages, then evaluates the steps taken to satisfy it. You only supply turns on the ConversationalTestCase.Does it account for tool calls when scoring the plan?
tools_called, and the metric factors tool usage into the plan it reconstructs and how well that plan reached the goal.