Your agent asked a question. Which part was slow?
An agent asks your data API a question. Three seconds later it answers. Someone asks why three seconds, and the honest response is a shrug — because the only thing anybody can see is that a tools/call went in and JSON came out. Was it the template? The database? A JWKS refresh nobody remembers configuring? A second query you didn't know existed?
You can put a service mesh in front of flAPI and it will tell you the request took three seconds. It cannot tell you which part. Only flAPI knows that, and until now it wasn't saying.
It is now. flAPI emits OpenTelemetry traces for every request on every route, adopts the trace context an MCP agent sends alongside its tool call, and reports what DuckDB actually did underneath. All of it is off by default, and when you turn it on it exports no customer data unless you explicitly opt an endpoint in.