Generic, configurable analytics component for Convex — any event, any dimension, any domain; rollup-on-write with funnels, retention, uniques
This is a Convex component, not an MCP server. The 18 tools are Convex functions (queries, mutations, actions) exposed via a Convex backend, not MCP tools. Tool definitions are inferred from TypeScript function signatures and package.json metadata, not from explicit MCP tool registration. Schemas are partially visible in the source but lack formal JSON Schema declarations. Descriptions are present but generic (10-100 chars, well below the 50-200 char LLM-optimized baseline). No error handling guidance, no output schema documentation, no parameter validation rules. The server cannot be evaluated as an MCP implementation because it is not one.
Re-derive rollups from raw events for a (scope, name). Idempotent: deletes existing rollup rows for the name, then recomputes from the retained raw events.
Close sessions idle past sessionIdleMs (set endTs). Idempotent.
Persist cron-relevant config (retention/sampling/idle) for the scope.
Histogram of a numeric measure: ascending upper-bound bins + overflow.
Ordered step conversion (generic, keyed by subjectRef).
Paginated raw events for an event name, newest first.
Total count over a range, optionally filtered by a dimension value.
HTTP GET endpoint to query total count over a range with optional dimension filter.
Not an MCP server. This is a Convex component with TypeScript function definitions, not an MCP tool server. Cannot be evaluated against MCP patterns.
Descriptions are too short (10-45 chars) and lack LLM-optimized guidance. Baseline for A+ tools is 50-200 chars with WHAT/WHEN/WHY context. E.g., 'track' says 'Ingest an event' but omits when to call it vs other tools, what happens on dedupe, or error cases.
No output schema documentation. Tools return data but no formal schema describes the response structure, field types, or pagination. LLMs cannot plan downstream calls without knowing what fields to expect.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 37 | 2026-07-28+ | v2 |
Delete raw events past retentionDays for a scope. Rollups are kept forever. Idempotent.
Cohort return rates by first-seen period.
Bucketed counts over a range.
HTTP GET endpoint to query bucketed counts over a range.
Top values of a dimension (breakdown).
HTTP GET endpoint to query top values of a dimension.
Ingest an event: rollup-on-write + raw event + counter. Sampling + dedupe applied.
HTTP POST endpoint to ingest an event with API key authentication.
DAU/WAU/MAU from subjects.
HTTP GET endpoint to query DAU/WAU/MAU from subjects.
No error handling guidance. Tools lack descriptions of failure modes, recovery steps, or actionable error messages. E.g., 'prune' and 'backfill' are destructive but offer no confirmation or dry-run pattern.
Endpoint tools ('trackEndpoint', 'metricEndpoint', etc.) use HTTP but are not registered as MCP tools. They are raw HTTP routes, not MCP-compliant tool definitions. Naming is also confusing, 'Endpoint' suffix signals HTTP routes, not tool names.