Use case

Build toward MCP tool-call observability from the edge.

Product direction: connect supported evidence about the initiating agent, user, device, client, MCP server, tool, downstream dependency, and outcome in one trace.

Talk to AxLoop
01

Client context matters

Server logs cannot explain attempts that fail before arrival, local configuration choice, or the device and user that initiated a call.

02

A complete trace

Useful traces connect identity, server, tool, model, latency, retries, status, policy, and downstream dependencies.

03

Portable telemetry

OpenTelemetry and W3C TraceContext allow tool-call evidence to connect across process and network boundaries without locking it to one backend.

04

Operational outcomes

Teams can investigate reliability, attribute cost, find shadow configurations, and understand data paths from the same connected evidence.

Common questions

Answers, briefly.

Why observe MCP tool calls from the client side?
The client knows which agent, user, and device started a call, which configuration it used, and whether the call failed before reaching the server. Server logs alone cannot provide that context.
What would a complete MCP trace contain?
Where supported, a future trace could include the initiating agent and client, user and device, MCP server and tool, model, timing, status, policy result, and downstream dependency. Missing or inferred fields must be labeled clearly.
Does tool-call observability need sensitive data?
Not by default. The product direction favors metadata-first traces. Any future content collection would require explicit organizational authorization plus filtering, redaction, and retention controls.
Which teams need MCP tool-call observability?
Platform teams need reliability context, security teams need unexpected-path evidence, and engineering or product teams need to understand whether agent-accessible capabilities work. These are target users for the product direction.

AxLoop AI

Start with evidence at the edge.

Discover what exists. Build toward understanding the interaction.

Book a working session