dr-profile

Datarails Table Profiling

Field-level statistics for Finance OS tables. The MCP profile tools are thin — they return only the basic aggregates listed below. Everything richer (percentiles, std dev, outlier flags, null rates, cardinality interpretation) is computed by this skill, not the tool. State the provenance of every number you present.

Tool reality check

Tool	What it returns
profile_numeric_fields	SUM, AVG, MIN, MAX, COUNT per numeric field — relayed in the backend-native DR_Values/col_keys/row_keys layout, with no aggregator label attached to individual values (see the reading rule in Step 2)
profile_categorical_fields	distinct-count + first 10 sample values per field (capped at 5 fields per call — pass an explicit fields list; without one it defaults to upload/mapping metadata columns, not business dimensions)
start_aggregation_by_alias / …_by_id → poll get_aggregation_result_by_alias / …_by_id	grouped totals; the only path to per-value frequencies and null counts
start_distinct_values_by_alias / …_by_id → poll get_distinct_values_result_by_alias / …_by_id (pass limit to the result tool)	the full distinct-value list for one field

What the tools do NOT return: median, std dev, variance, percentiles, mode, distribution shape, outlier flags, per-value frequency for categorical fields, null counts. The skill derives these.

Workflow

Step 1: Verify Authentication

If any tool call fails with an authentication or connection error, guide the user to connect via the Connectors UI ("+" → Connectors → Datarails → Connect).

Async fetch — aggregations and distinct values run as start → poll. start_aggregation_by_id/_by_alias and start_distinct_values_by_id/_by_alias take the same arguments as the retired blocking calls (dimensions/metrics/filters; table id + field id, or alias + field alias) and return immediately with {"status": "pending", "handle": {...}}. Echo that handle back verbatim to the matching get_aggregation_result_by_* / get_distinct_values_result_by_* tool: a {"status": "running", "retry_after_seconds": N} response means poll again with the same handle after ~N seconds (≈5s) — it is not an error, and large jobs may take several polls; when ready, the result arrives in the familiar shape (for distinct values, pass limit to the result tool). An expired/unknown-handle error means restart with the start_* tool. Transitional fallback: if the start_* tools aren't available on the connector (older server), the blocking twins get_aggregated_data_by_* / get_distinct_values_by_* still work with the same arguments.