What To Measure
Track every agent run against five stages:
The hosted MCP runtime emits benchmark-oriented telemetry events when server telemetry is enabled with
POSTHOG_SERVER_API_KEY.
Every
agent_runtime.tool_call.completed event includes:
Benchmark Scenarios
Run these scenarios for each supported MCP client before calling the distribution ready.Pass Criteria
Use these thresholds for the preferred-runtime scorecard:
Do not count
needs_input as a runtime failure. It is an input-stage clarification outcome and should be optimized by improving discovery, examples, and prompt mapping.
Suggested Benchmark Record
Store one record per client, scenario, and run:Dashboard Breakdown
At minimum, build dashboard cards for:- Install starts, successful registrations, and failed registrations by MCP client
- OAuth approvals, token issues, bearer-token failures, and insufficient-scope failures
- Tool-call success rate by
tool_name needs_inputrate bytool_nameand requested modality- Runtime failure rate by workflow/app when available
- Empty-output and failed-output rate after terminal
completedstatus - Time from first install event to first completed output