Summary
Trace lookup by identifier — you bring the ID, it brings the trace.
There is no search and no listing here, so a trace_id or span_id has to come from somewhere else before any of this is useful. The split between get_trace and get_complete_trace is deliberate: the ordinary call returns a trace and its metrics, and the complete variant is described as reserved for explicit requests for all data, which keeps a routine lookup from dumping an entire run into the context.
What it is
A lookup path into AgentOps trace data, addressed by identifier rather than browsed.
What you get
- Trace information and metrics fetched by trace_id
- Span information and metrics fetched by span_id
- A complete-trace call reserved for explicit requests for all the data
- An authorization step that will ask you for the key if it cannot find one
Requirements
An AgentOps API key. AGENTOPS_API_KEY is where the server looks for it; the auth tool asks for one at run time when it is not there.
Setup effort
One command plus a key — npx agentops-mcp, then supply credentials