[data-reveal]{opacity:1!important;transform:none!important}
AntelopeJS DMS
DocumentationConnected database values

Connected database values

What the DMS MCP tools answer about a connected database and the modules mapped from it, and which values from its rows they leave out.

A tool's answer reaches the AI provider, the assistant's saved state and the chat. So the tools that read a connected database answer its shape, never a value from its rows.

What each tool leaves out

ToolAnswersLeaves out
database_relations, database_describeNames, native types, nullability, defaults, enum labels, comments, keys, indexes, references and row estimates.Nothing, since none of it comes from a row.
database_profileRow counts, and per column the nulls, distinct values, text lengths, traits, the number of months that hold rows, and the rows per category. The fan-out of references.The range of a number, date or enum column, the category values and the month labels.
builder_analyse_database, builder_mappingThe proposal or mapping, with each field's traits, nulls, distinct values and rows per category. A badge reads { "kind": "badge", "values": 3 } and a price reads { "kind": "price" }.The value ranges, the category values, the badge items and the price currency.
builder_map_resourcesThe files it wrote, the columns it left out and its warnings.The diff of each file.
builder_resource_structure, builder_page_structure on a file mapped from a connected database, or a file that imports oneThe structure. Each select's items, price's currency and TableView's tabs that a mapping wrote read { "$hidden": n }, where n counts the values. Values the AI wrote itself read as written.The badge items, the tab labels and filter values, and the currency a mapping wrote.
Every builder tool that edits such a fileEach changed file's path and kind.The diff of each file.
builder_preview_querystatus (ok, empty or zero) and the types of the answer's body, such as "string" or { length, items } for a list.Every value of the body.
builder_compose_page with preview: trueEach block's status (ok, empty, zero or error) and its answer's types.Every value of the answers.
page_verifyThe render, each block's data state and source path, the permissions, each control by its kind and position (such as tab #2), each console error by its class (such as TypeError), and the path of a failed request when a block of the page reads that path.The names on the page's controls and menus, console messages, queries, other paths (shown as /…), the origin of a request to another server (shown as other origin), and screenshots.

The builder still uses the values

The builder reads the values inside the DMS, where they never reach the AI. builder_map_resources writes a badge sent as { "kind": "badge" }, or left out, with the items the relation's mapping holds, else the items the analysis proposes. A price sent without a currency gets the currency the mapping holds, else the one the analysis proposes. To write a currency neither holds, send it.

The onboarding screen's analysis and its Build button run without the AI, and show the values.

Editing a hidden value

A tool that changes the project refuses arguments that hold a $hidden value. To keep what the code holds, leave that key out of the patch:

  • builder_configure_field with only a label keeps the badge.
  • builder_configure_block with only a caption keeps the tabs.
  • builder_configure_block with replace: true is refused while it would drop a hidden option.
  • builder_map_resources with tabs: null removes the tabs it wrote.

A badge column still takes a new label, order or visibility, can group a kanban board, and can take another DataType. Without the items, the AI cannot relabel or recolour one badge item, or add a tab for a value.

How the DMS knows a value came from rows

Each mapping records in the module's package.json, under dmsBuilder.database.rowLiterals, a SHA-256 digest of each value it wrote from rows: each select item's value, each tab's filter value and each currency. A select, a tab or a currency that holds one of those values reads hidden wherever it goes, so a mapped page moved to another category keeps its tabs hidden.

A module mapped before these digests existed, one whose record cannot be read, and one that a mapping is writing now have every such value hidden. The first mapping after the upgrade records the values.