Valiqor automatically traces AgnoDocumentation Index
Fetch the complete documentation index at: https://docs.valiqor.com/llms.txt
Use this file to discover all available pages before exploring further.
Agent.arun() calls, capturing the full
agent lifecycle including model interactions, tool executions, and MCP
tool schemas.
Agno tracing requires the
agno package to be installed separately.
There is no valiqor[agno] extra — install agno directly alongside
valiqor.Install
Zero-Config (Recommended)
Add a single import at the top of your app — all Agno agent runs are automatically traced:Selective Instrumentation
If you only want Agno tracing:Tool Call Tracing
When your Agno agent uses tools, each tool execution is captured as a child span with full details:| Field | Description |
|---|---|
tool_name | Name of the tool |
call_id | Unique tool call identifier |
arguments | Raw and parsed arguments |
result | Tool output content |
error | Error info (if failed) |
description | Tool description |
execution_metrics | Performance data |
MCP Tool Support
Agno’s MCP (Model Context Protocol) tool integration is automatically detected. When your agent uses MCP tools, Valiqor captures the MCP server metadata and tool schemas:What Gets Captured
Each traced Agno agent call records:| Field | Description |
|---|---|
model | Model name from agent instance |
message | User input message |
response | Agent response content |
prompt_tokens | Input token count |
completion_tokens | Output token count |
total_tokens | Combined token count |
cost | Estimated cost in USD |
tool_calls | Full tool call details (see above) |
mcp_tools | MCP server info and tool schemas (if any) |
duration_ms | Total agent run latency |
status | Success or error |
With Workflows
Group multiple agent interactions into a single trace:research-and-write trace.
Disabling
Limitations
- Async only — only
Agent.arun()(async) is traced. SynchronousAgent.run()is not instrumented. Useasyncio.run()for sync entry points. - Streaming is not instrumented.
- Team orchestration — multi-agent team runs are traced at the individual agent level, not at the team coordination level.
Next Steps
Tracing Guide
Learn about traces, spans, workflows, and exporters.
Failure Analysis
Run failure analysis on your traced agent calls.