Connected database values
What the MCP tools of the DMS answer about a connected database and a module mapped from it, and which values read from its rows they leave out.
A tool 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:
| Tool | Answers | Leaves out |
|---|---|---|
database_relations, database_describe | names, native types, nullability, defaults, enum labels, comments, keys, indexes, references, row estimates | nothing: none of it comes from a row |
database_profile | rows, the sample, and per column nulls, distinct, text lengths in characters, traits, months as the number of months that hold rows, and categories as the rows of each category and other; fan-out and the share of a reference's values found in its target | the range of a number, date or enum column, the category values and the month labels |
builder_analyse_database, builder_mapping | the proposal or mapping, each field's traits, nulls, distinct and rows per category, a badge as { "kind": "badge", "values": 3 }, a price as { "kind": "price" } | the value ranges, the category values, the badge items and the price currency |
builder_map_resources | the files it wrote, the columns it left out, its warnings | the diff of each file |
builder_resource_structure, builder_page_structure on a file of a module mapped from a connected database, or a file that imports from one, such as a mapped page moved into another category or a page built over a mapped resource | the structure, with a select's items, a price's currency and a TableView's tabs as { "$hidden": n }, n the values they hold | the badge items, the tab labels and filter values, and the currency |
| every builder tool that edits such a file | each changed file's path and kind | the diff of each such file |
builder_preview_query | status (ok, empty when no rows, zero when every figure is zero or missing) and the body's types: each leaf as "string", "number", "boolean" or "null", each list as { length, items } with the distinct types of its elements | every value of the body |
builder_compose_page with preview: true | each block's status (ok, empty, zero, error) and its answer's types, as builder_preview_query gives them | every value of the answers |
page_verify | the render, each block's data state and source path, the permissions, each link, tab, column, search, form or button by its kind and an ordinal, such as tab #2, each console error by its class, such as TypeError, and the path of a failed request or a held-back write when a block of the run reads that path | the names the page shows on its controls and menus, console messages, queries, the origin of a request to another server, shown as other origin, and any other path, shown as /… since it can hold a record key, and any screenshot |
The Builder still reads the values inside the DMS. builder_map_resources writes a badge sent as { "kind": "badge" }, or left out, with the items the relation's mapping holds, else the ones the analysis proposes from the profile. A price sent without a currency, such as { "kind": "price" } as the proposal shows it, is also the one the Builder reads itself: the price the relation's mapping holds, else the one the analysis proposes, in the code the column comment states or the one code a currency column of the relation holds. To write a price neither holds, send its currency. The onboarding screen's analysis and the Build button run without the AI and show the values.
A tool that changes the project refuses arguments holding a $hidden value. To keep what the code holds, leave that key out of a patch: builder_configure_field with only a label keeps the badge, and 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. A badge column still takes a new label, order or visibility, groups a kanban (builder_configure_table_view), and can be given another DataType with builder_configure_field. builder_map_resources with tabs: null removes the tabs it wrote. Without the items, the AI cannot relabel or recolor one badge item, add a tab for a value, or change another option of the badge's DataType, since a dataType patch replaces the items.