evals: AgentConfig.from_agent raises AttributeError for workflow / non-LlmAgent root agents (no 'tools' field)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start with _get_tool_declarations_from_agent and AgentConfig.from_agent in vertexai/_genai/types/evals.py, then compare the mirrored agentplatform/_genai/types/evals.py copy. Run the SequentialAgent reproduction and exercise the run_inference and AgentInfo.load_from_agent paths. Done means workflow roots no longer raise AttributeError, report no root tools, and still recurse into sub_agents.
Written by the indexing model from the issue text.
Description
Environment
google-cloud-aiplatform: 1.156.0google-adk: 2.2.0- Python: 3.12
Summary
vertexai.types.evals.AgentConfig.from_agent() raises AttributeError when the root agent is a workflow / non-LlmAgent agent — i.e. any BaseAgent subclass such as SequentialAgent, ParallelAgent, LoopAgent, or a custom BaseAgent. Those agents do not define a tools field; only LlmAgent does.
_get_tool_declarations_from_agent reads agent.tools directly (no default), whereas the sibling fields in from_agent (description, instruction, sub_agents) all use getattr(agent, ..., default). As a result, introspection fails before any inference runs, which makes client-side eval impossible for any multi-agent system whose root is an orchestrator.
This affects every public entry point that introspects a live agent:
client.evals.run_inference(agent=...)→AgentConfig.from_agent(agent)types.evals.AgentInfo.load_from_agent(agent=...)→AgentData.get_agents_map(agent)→AgentConfig.from_agent(agent)
Reproduction
from google.adk.agents import LlmAgent, SequentialAgent
from vertexai import types
leaf = LlmAgent(name="step", model="gemini-2.5-flash", instruction="do a step")
wf = SequentialAgent(name="pipeline", sub_agents=[leaf])
types.evals.AgentConfig.from_agent(wf)
Actual behavior
Traceback (most recent call last):
File ".../vertexai/_genai/types/evals.py", line 128, in from_agent
tools=AgentConfig._get_tool_declarations_from_agent(agent),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File ".../vertexai/_genai/types/evals.py", line 86, in _get_tool_declarations_from_agent
for tool in agent.tools:
^^^^^^^^^^^
File ".../pydantic/main.py", line 1042, in __getattr__
raise AttributeError(f'{type(self).__name__!r} object has no attribute {item!r}')
AttributeError: 'SequentialAgent' object has no attribute 'tools'
The same failure occurs via client.evals.run_inference(agent=wf) and types.evals.AgentInfo.load_from_agent(agent=wf), since both reach AgentConfig.from_agent.
Expected behavior
from_agent should treat a missing tools field as "no tools", consistent with how it already handles instruction and sub_agents. A workflow root with LlmAgent leaves should produce an AgentConfig with empty tools for the root and recurse into sub_agents normally.
Suggested fix
In _get_tool_declarations_from_agent (vertexai/_genai/types/evals.py, and the mirrored agentplatform/_genai/types/evals.py copy), iterate over a guarded value:
for tool in getattr(agent, "tools", None) or []:
...
This mirrors the existing getattr(...) usage for the other fields in from_agent.
Related
Distinct from #6861 / #6862, which addressed a TypeError for toolset elements within tools (e.g. McpToolset). Here the tools attribute is absent entirely. Both point at the same fragile extraction path.
Workaround
Inject an empty list before introspection:
if not hasattr(root_agent, "tools"):
object.__setattr__(root_agent, "tools", [])
- Dominant language
- Python
- Stars
- 907
- Forks
- 467
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 40
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from googleapis/python-aiplatform
-
api: vertex-ai
Difficulty 1/5 Under an hour Newbie friendliness 85/100
googleapis/python-aiplatform#7132 ·
-
api: vertex-ai
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
googleapis/python-aiplatform#7097 ·
-
CustomContainerTrainingJob.run drops max_wait_duration=0 instead of requesting indefinite DWS wait Openapi: vertex-ai
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
googleapis/python-aiplatform#7067 · 1 comment ·
-
api: vertex-ai
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
googleapis/python-aiplatform#6877 ·
-
api: vertex-ai
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/python-aiplatform#6822 · 2 reactions ·
All issues in googleapis/python-aiplatform
Similar issues
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/open-webui#30750 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
OpenwaterHealth/openmotion-bloodflow-app#604 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100