{
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"name": "<string>",
"mentions": "<unknown>",
"order": 123,
"created_by": "<string>",
"created_at": "2023-11-07T05:31:56Z",
"updated_at": "2023-11-07T05:31:56Z",
"content": "<string>",
"folder": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}Semantic Layer
Semantic Layer document object
A document is a markdown note that teaches Nekt — and any assistant reading through MCP — what your
data means: metric definitions, business rules, caveats a column name cannot carry.
Two fields deserve a word:
| Field | |
|---|---|
content | The markdown body. Mentions written as @type::identifier (for example @table::silver.orders) are parsed out of it server-side. |
mentions | Read-only. The parsed result of the above — send content, never this. |
folder places the document in the tree; omit it (or send null) to leave it at the root.
Related
- Create a document and Update a document.
- List Semantic Layer Documents — the read, with its filters.
- Semantic Layer — what the module is and how it is used in the app.
Maximum string length:
255Manual position among its siblings; NULL falls back to created_at ordering.
Created by (Expandable)
Folder to place the document in. Omit or send null to put it at the root.
Was this page helpful?