Skip to content

How to implement that is written in the doc. I can't find code reference. #3440

Closed

Description

@miyannishar

how to implement these evaluations types in the tools trajectory.

Activity

  1. added
    eval[Component] This issue is related to evaluation
    on Nov 7, 2025
  2. llalitkumarrr commented on Nov 7, 2025

    @llalitkumarrr
    Collaborator

    Hello @miyannishar

    Could you please elaborate on your question a bit more so that we can understand your query clearly and assist you better?

  3. miyannishar commented on Nov 7, 2025

    @miyannishar
    Author

    I am implementing the Evaluation of my Agentic System using pytest and I want to test the agent if its calling the tools in a series. Here in the docs its mentioned that we can evaluate the agent's tool call using exact match, in order, any order precision and so on so forth but for implementation, we only have one criteria: tool_trajectory_avg_score that only look for exact match. My question is how to implement the evaluation of tool call based on any order match instead of exact match only.

    I am using LiteLLM, so using LLMAsAJudge is not an option for me.

  4. llalitkumarrr commented on Nov 7, 2025

    @llalitkumarrr
    Collaborator

    Hello @miyannishar,

    Here on this page, you can find all the Evaluation Criteria available with ADK. If the tool_trajectory_avg_score metric doesn’t meet your requirement, you could explore rubric_based_tool_use_quality_v1. It is important to note that this evaluation method uses an LLM as a judge.

    At present, these two are the recommended criteria for evaluating tool trajectories.

  5. locked and limited conversation to collaborators on Nov 7, 2025
  6. converted this issue into a discussion #3448 on Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

eval[Component] This issue is related to evaluation

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions