Manage Data Store

​

What it does

• create_store creates a brand-new data store (name + optional description) — no knowledge_base_id needed. Use it when work deserves its own store rather than adding unrelated tables to an existing one. Creation only: deleting stores stays with manage_knowledge_bases.

​

Parameters

​

Key behaviors

• A primary key is added for you. create_table adds an id primary key automatically unless you define your own.
• Views give apps aggregation power. create_view stores an agent-authored SELECT that apps read like a table — the way to let an app show a rollup or join over a large table without pulling every row. Views run with the reading role’s privileges, so they stay safely scoped to the store.
• Destructive changes are gated. Dropping a column, table, or view requires confirm: true, because a published app may depend on it.
• Locked stores refuse structure changes. If the store’s creator has locked it, every operation except describe fails unless the requesting user is its creator or an org admin. Rows stay writable through write_data_store. manage_knowledge_bases list shows locked and canEdit for locked stores.
• Every change is audited, and the store’s cached schema — which the agent sees in its context — refreshes automatically after each change.

​

Common use cases

​

Create a table

operation: create_table
knowledge_base_id: 954
table: project_stages
columns:
  - { name: stage_name, type: text, nullable: false }
  - { name: status, type: text, nullable: false }
  - { name: sort_order, type: integer, nullable: false }

​

Create a view for an app to chart

operation: create_view
knowledge_base_id: 954
table: stage_summary
view_sql: SELECT status, count(*) AS n FROM project_stages GROUP BY status

​

Related

• Query Data Store — read data with SQL
• Write Data Store — insert, update, delete, upsert
• Data Stores — the feature overview