Skip to main content
You will record a local order lookup and inspect its span tree through MCP. The example application makes no model calls and needs no external dataset. Enabled platform scoring can still invoke models after trace ingestion.

Before you begin

Connect Overmind, select your tutorial project and open an empty working directory with Python available. Configure its API key through your environment’s secret mechanism. MCP login alone does not configure the Python SDK’s telemetry credentials. This prompt requests one local run and its telemetry upload. If credentials or host permissions are missing, complete that setup before the agent runs it.

Inspect the code it creates

The central tracing code should have this shape. The agent supplies a unique conversation ID and the verified deployment configuration:
The agent installs overmind[tracing] in an isolated environment, runs the script once and queries the session using query_traces. The run flushes buffered telemetry when its context exits.

Check your result

Expect the local output to contain order A-1001 with status shipped. The matching trace should have an order-status root and child spans for lookup_order and delivery. Inspect the actual captured input and output, not just the span names. There should be one trace for the unique session. If none arrives, the agent checks credentials, destination and flush behaviour. A retry should be reported as another execution. No capability is declared in this lesson. The trace can remain unbound while still being inspectable.

Try a follow-up

For your own application, continue with Map an agent repository and Instrument an application.