get_object
Full detail for one business object: agent-oriented description, row_count (data rows in its primary export) and grain (the columns that identify one row — null when none was found), fields (each field whose column is in the export with a role — identifier, dimension, measure or attribute, derived from the export, with role_basis naming the rule that gave it — and a profile of counts only: the column type, filled and blank rows, and distinct values, never a value; role and profile are absent where the field was not assessed; and every field with an explicit pii flag and a personal-data classification: category none/contact/identity/financial/special-category/other-personal, where it came from — the column name, the shape of the values as counts, or the customer — and its confidence), source systems, every relation touching it (with strength, join key and row coverage — the share of rows that actually reach the other side), the findings that mention it, and the automations your human’s systems run that read or write it (automations, when the workspace keeps a registry — see list_automations). Fields with pii=true hold personal data — never select or echo their values from source systems unless the task explicitly requires it.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Object name as the map spells it — the name search, route and the object pages hand out, e.g. "invoice" or "Invoice". A name written entirely in lower case is matched too. |