Fibery

Issue a short-lived (~1 hour) access token for developing a custom app locally. The token authenticates only the app's `get-source-files` / `update-source-files` endpoints, passed as the `custom-app-dev-token` query parameter — see `get_fibery_skill({skill: "custom-apps-dev"})` for the full development loop.

create_custom_app_dev_token

Creates one or more new databases within a space. The following system fields are created automatically and should NOT be added manually: - fibery/id, fibery/public-id, fibery/creation-date, fibery/modification-date, fibery/created-by, fibery/modified-by - {Space}/Name (title field) - {Space}/Description (rich text document field) Naming restrictions: database names may contain ONLY letters, numbers, and spaces. Special characters (/, \, ., &, ,, ?, !, etc.) are NOT allowed. Prerequisites: call `schema` to check existing spaces and databases. ## Example ``` { "databases": [ {"name": "SoftDev/Task", "description": "Task management database", "color": "#4CAF50"}, {"name": "SoftDev/Story", "description": "User stories"} ] } ```

create_databases

Creates entities. Prerequisites: call `schema` and `schema_detailed` first to discover database names and field names. The following system fields are populated automatically and are READ-ONLY: - fibery/id - fibery/public-id (human-friendly auto-increasing id) - fibery/creation-date - fibery/modification-date - fibery/created-by - fibery/modified-by Restrictions: - You cannot set fibery/id. You can read it from the tool result. - You cannot populate 'Collaboration~Documents/Document' fields using create_entities. Use `insert_document_blocks` instead. - You cannot populate Collection field using create_entities. Use `add_collection_items` instead. - You cannot set 'workflow/state' field using create_entities. Use `set_state` instead. - NEVER pass arrays as field values in create_entities - use `add_collection_items`. Not following Restrictions will ALWAYS result in an error. ## Examples 1. Entity creation: ``` { "database": "Product Management/Feature", "entities": [{ "Product Management/Name": "Advanced Search Functionality", // text field "Product Management/Pain Level": 5, // int field "Product Management/Release Date": "2024-12-31", // date field "Product Management/Dates": { // date-range, pass JSON object with start and end dates. IMPORTANT: the last day of end date is NOT included, i.e., if user asks for range from July 31st to Aug 2nd, the date-range field value must be `{"start": "2025-07-31", "end": "2025-08-03"}` "start": "2024-12-31", "end": "2025-01-10" }, "Product Management/Is Critical": true, // boolean field "Product Management/Parent Feature": "<uuid>", // relation to a single entity, pass uuid "Product Management/Priority": "<uuid>", // single-select field, pass uuid of the option }] } ``` 2. Populating relations and single-select fields: BAD: `{"Product Management/Priority": {"id": "<uuid>"}}` - passing object will be REJECTED GOOD: `{"Product Management/Priority": "<uuid>"}` - pass id as a string

create_entities

Creates one or more file attachment fields in databases. Each files field is a reference to the built-in fibery/file database. Naming restrictions: field names may contain ONLY letters, numbers, and spaces. Special characters (/, \, ., &, ,, ?, !, etc.) are NOT allowed. Prerequisites: call `schema` to get database names. ## Example ``` { "fields": [ { "database": "SoftDev/Task", "name": "SoftDev/Files", "allowMultipleFiles": true, "description": "Task file attachments" } ] } ```

create_files_fields

Creates a formula field in a database. The formula expression is generated automatically based on the provided description. Naming restrictions: field names may contain ONLY letters, numbers, and spaces. Special characters (/, \, ., &, ,, ?, !, etc.) are NOT allowed. Prerequisites: call `schema` to check existing spaces and databases. Call `schema_detailed` to see available fields in the database. ## Example ``` { "database": "SoftDev/Task", "name": "SoftDev/Days Since Created", "description": "Number of days since the entity was created" } ```

create_formula_field

Enables emoji icons on entities in one or more databases. Creates an "icon/icon" field automatically. Prerequisites: call `schema` to get database names. ## Example ``` { "databases": ["SoftDev/Task"] } ```

create_icon_fields

Creates one or more multi-select fields with predefined options in databases. Prefer select fields to bare text fields whenever feasible — they improve UX dramatically. Naming restrictions: field names may contain ONLY letters, numbers, and spaces. Special characters (/, \, ., &, ,, ?, !, etc.) are NOT allowed. Prerequisites: call `schema` to get database names. ## Example ``` { "fields": [ { "database": "SoftDev/Task", "name": "SoftDev/Tags", "options": [ {"name": "Frontend", "color": "#2196F3"}, {"name": "Backend", "color": "#4CAF50"}, {"name": "DevOps", "color": "#FF9800"} ] } ] } ```

create_multi_select_fields

Creates one or more primitive fields in databases. Avoid using bare text fields (`fibery/text` without meta). Consider using `create_single_select_fields`, `create_multi_select_fields`, `create_relation_fields`, tools to create a more suited field, or a text field using this tool with specific meta (email, url, phone). Naming restrictions: field names may contain ONLY letters, numbers, and spaces. Special characters (/, \, ., &, ,, ?, !, etc.) are NOT allowed. Prerequisites: call `schema` to get database names. Call `schema_detailed` to check existing fields. Creating already-existing field will result in an error. ## Supported field types - `fibery/text` — text field (meta: `ui/type` can be 'text', 'email', 'url', 'phone') - `fibery/int` — integer number - `fibery/decimal` — decimal number. Meta: - `ui/number-format`: 'Number', 'Money' or 'Percent' - `ui/number-currency-code`: currency code in ISO 4217 format - `ui/number-thousand-separator?`: true | false - `ui/number-precision`: number in range of 0-8 - `ui/number-unit`: string, custom unit (like "$", or "%") - `fibery/bool` — checkbox - `fibery/date` — date - `fibery/date-time` — date and time - `fibery/date-range` — date range - `fibery/date-time-range` — date and time range - `fibery/location` — location/address - `Collaboration~Documents/Document` — rich text document ## Example ``` { "fields": [ { "database": "SoftDev/Task", "name": "SoftDev/Budget", "fieldType": "fibery/decimal", "meta": {"ui/number-format": "Money", "ui/number-currency-code": "USD", "ui/number-precision": 2, "ui/number-thousand-separator?": true} }, { "database": "SoftDev/Task", "name": "SoftDev/Email", "fieldType": "fibery/text", "meta": {"ui/type": "email"} } ] } ```

create_primitive_fields

Creates one or more relation fields between databases. Each relation creates a field in both the source and target databases. Naming restrictions: field names may contain ONLY letters, numbers, and spaces. Special characters (/, \, ., &, ,, ?, !, etc.) are NOT allowed. Prerequisites: call `schema` to get database names. Call `schema_detailed` to check existing fields. ### Cardinality options - `one-to-one` - `one-to-many` - `many-to-one` - `many-to-many` ## Example ``` { "fields": [ { "database": "Planning/Feature", "relationDatabase": "SoftDev/Story", "name": "Planning/Stories", "relationFieldName": "SoftDev/Feature", "cardinality": "one-to-many", "description": "Collection of Stories linked to a Feature" } ] } ```

create_relation_fields

Creates a Fibery report with sources and a title. The report is placed in the user's private space unless `spaceName` is provided. Prerequisites: call `schema` to discover valid database names; call `display_report_schema` to discover field expressions before configuring dimensions. Reports are a specialized domain — call `get_fibery_skill` with `skill: "reports"` for the full report model, expression syntax, palettes, conditions, and workflow.

create_report

Creates one or more single-select fields with predefined options in databases. Prefer select fields to bare text fields whenever feasible — they improve UX dramatically. Naming restrictions: field names may contain ONLY letters, numbers, and spaces. Special characters (/, \, ., &, ,, ?, !, etc.) are NOT allowed. Prerequisites: call `schema` to get database names. ## Example ``` { "fields": [ { "database": "SoftDev/Task", "name": "SoftDev/Priority", "options": [ {"name": "Low", "color": "#4CAF50"}, {"name": "Medium", "color": "#FF9800"}, {"name": "High", "color": "#F44336", "icon": ":fire:"} ], "defaultOption": "Medium" } ] } ```

create_single_select_fields

[//]: # (Creates a new space in the workspace.) Naming restrictions: space names may contain ONLY letters, numbers, and spaces. Special characters (/, \, ., &, ,, ?, !, etc.) are NOT allowed. Prerequisites: call `schema` to check existing spaces. ## Example ``` { "name": "SoftDev", "description": "Software development space", "color": "#4CAF50" } ```

create_space

Creates a View in the Fibery workspace — a saved data visualization (grid, list, board, timeline, calendar, map, feed, gallery, gantt, embed), a form, a standalone document, or a whiteboard (canvas). **For anything more complex than a flat grid/list with no filters, no orderBy, no grouping, and no color coding — call `get_fibery_skill({skill: "views"})` FIRST.** That reference covers per-view-type config shapes, the FilterNode operator matrix, conditional color coding, multi-database axes, hierarchy via groupBy, dependency rules for timeline/gantt, form defaultValue formats, and worked examples. Skipping it on non-trivial views leads to invalid configs and retries. Prerequisites: call `schema` (and `schema_detailed` for field details) to discover database and field names. Trivial example — flat grid, no filter or ordering: ```json { "viewType": "grid", "name": "All Features", "config": { "items": [{ "database": "Product/Feature", "fields": [{"field": "Product/Name"}, {"field": "Product/Status"}] }] } } ``` Document view — no `config`; the view is created with an empty body. Content CANNOT be set via this tool — after creating, write the body with the document block tools (call `get_fibery_skill({skill: "documents"})` first): ```json { "viewType": "document", "name": "Meeting Notes" } ``` Canvas (whiteboard) view — no `config`; the board is created empty. Only use it when a user asks to create a new Whiteboard. To add elements, call `execute_whiteboard_commands` with the returned `id` — call `get_fibery_skill({skill: "whiteboard"})` first: ```json { "viewType": "canvas", "name": "Sprint Retro", "description": "Retro board for sprint 42" } ```

create_view

Creates a workflow (state) field for tracking entity status through stages. Only ONE workflow field can exist per database. The field is always named "workflow/state". Use this for process or status tracking (e.g., task states, bug status). Do NOT use regular single-select for status-like fields. Prerequisites: call `schema` to get database names. Call `schema_detailed` to verify no workflow field exists yet. ## Example ``` { "database": "SoftDev/Task", "options": [ {"name": "To Do", "type": "Not started"}, {"name": "In Progress", "type": "Started", "color": "#2196F3"}, {"name": "Done", "type": "Finished", "color": "#4CAF50"} ], "defaultOption": "To Do" } ```

create_workflow_field

Permanently deletes an automation rule or button. To modify an automation, use `update_automation` instead of deleting and recreating it. ## Example ``` { automationType: "button", id: "123" } ```

delete_automation

Disables avatar/profile picture attachments on entities in one or more databases by deleting the "avatar/avatars" field. The field can be restored later by the user via the Activity Log. Prerequisites: call `schema_detailed` to verify the avatars field exists. ## Example ``` { "databases": ["SoftDev/Task"] } ```

delete_avatars_fields

Disables comments on entities in one or more databases by deleting the "comments/comments" field. The field can be restored later by the user via the Activity Log. Prerequisites: call `schema_detailed` to verify the comments field exists. ## Example ``` { "databases": ["SoftDev/Task"] } ```

delete_comments_fields

Deletes one or more databases from a space. The databases can be restored later by the user via the Activity Log. Prerequisites: call `schema` to get database names. ## Example ``` { "databases": ["SoftDev/Task", "SoftDev/Story"] } ```

delete_databases

Deletes blocks from a document, each with all its children. Call `read_document` first to get block ids. Call `get_fibery_skill({skill: "documents"})` for the block model and the editing workflow. Delete a `table` only by the whole `table` block's id — `table_row`, `table_cell` and `table_header` CANNOT be deleted, adding/removing rows or columns is not supported. ## Example ``` { secret: "123", blockIds: ["456", "789"] } ```

delete_document_blocks

Deletes entities by their IDs. Permanently removes entities from the specified database. This action cannot be undone. Prerequisites: call `schema` to get database names. Use `query` to find the entity IDs. ## Example ``` { "database": "SoftDev/Task", "ids": ["123", "456"] } ```

delete_entities

Deletes one or more fields from their databases. Fields can be restored later by the user via the Activity Log. If you delete a relation field, the corresponding relation field from the related database will also be removed automatically — no need to delete it separately. Prerequisites: call `schema_detailed` to get field names. ## Example ``` { "fields": [ {"database": "Planning/Feature", "field": "Planning/Stories"}, {"database": "Planning/Feature", "field": "Planning/Files"} ] } ```

delete_fields

Disables emoji icons on entities in one or more databases by deleting the "icon/icon" field. The field can be restored later by the user via the Activity Log. Prerequisites: call `schema_detailed` to verify the icon field exists. ## Example ``` { "databases": ["SoftDev/Task"] } ```

delete_icon_fields

Deletes a space from the workspace. Fibery-specific spaces (like fibery/user or fibery/files) cannot be deleted. All databases within the space will also be deleted. The space can be restored later by the user via the Activity Log. Prerequisites: call `schema` to get space names. ## Example ``` { "name": "SoftDev" } ```

delete_space

Delete Fibery Views by their IDs. The data present on the views WILL NOT be deleted. This action can be undone by the user via the Activity Log (by selecting the view and restoring it). Prerequisites: use `query_views` to find view IDs. ## Example ``` { "ids": ["123"] } ```

delete_views

Deletes the workflow (state) field from a database. The field can be restored later by the user via the Activity Log. Prerequisites: call `schema_detailed` to verify the workflow field exists. ## Example ``` { "database": "SoftDev/Task" } ```

delete_workflow_field

Returns the catalog of automation actions available for a database (action names, argument ids and accepted value shapes). The action catalog differs per database and per automation type, so ALWAYS call this before `create_automation` or before adding/changing actions with `update_automation`. Call `get_fibery_skill({skill: "automations"})` first for value types, trigger shapes and the FilterNode format. ## Example ``` { automationType: "rule", database: "SoftDev/Task" } ```

display_automations_schema

Returns per-entity capabilities derived from sharing for the requested Fibery databases. Use this when the user wants to know what access they have at the entity level (not just space- or database-level). For each database, the response includes the entities they can reach and how they reach them. Three access paths are covered: 1. **Direct sharing** — the entity was explicitly shared with the user, returned in `entityLevelGrants`. 2. **Propagated sharing** — access was inherited from a related entity, returned in `indirectEntityLevelGrants`. 3. **Assignment rules** — the user appears in a People-field rule on the entity type, returned in `assigneeGrants`. Capabilities from every source (space-level, database-level, per-entity grants, propagation from other databases) ACCUMULATE — they NEVER override. To compute effective capabilities on a specific entity, take the UNION of all sources. Limitations for assignee grants: sample only (up to 10 entities per rule) Per-database result fields: - `spaceLevelCapabilities` — capabilities granted at the space level. - `databaseLevelCapabilities` — capabilities granted at the database level. - `entityLevelGrants` — per-entity grants from direct sharing. - `indirectEntityLevelGrants` — grants propagated from related entities. - `assigneeGrants` — grants derived from assignment rules on People-type fields. If a database can't be resolved in the schema, its entry is `{database, error}` instead.

display_entity_capabilities_via_sharing

Get the vizydrop report source schema for one or more Fibery databases. This is distinct from the Fibery type/relation schema returned by `schema` or `schema_detailed`. Returns the flat set of fields and enum values usable in report dimension/metric expressions and filter conditions. Call this before configuring chart, table, or metric dimensions so you know the valid field names and types. **`sourceMode`**: `current` (default) for live entity state; `historical` for modification events (time-in-state data). When multiple databases are specified, a synthetic `Entity Database` field is added to allow splitting results by source. Reports are a specialized domain — call `get_fibery_skill` with `skill: "reports"` for the full report model, expression syntax, palettes, conditions, and workflow.

display_report_schema

Returns the current user's access info per space and per database in the Fibery workspace. Use this when explaining what the user can/cannot do, or before suggesting an action that requires specific access. URL conventions: - For spaces: user will see anything if they have ANY access to the space. - For databases: user will see anything only if they have architect-level access; otherwise it will render as "No Access". Capabilities from every source (space-level, database-level, per-entity grants, propagation from other databases) ACCUMULATE — they NEVER override. To compute the user's effective capabilities on a specific entity, take the UNION of all sources. The response shape: - `accessInfo.spaces` — map keyed by space namespace. - `accessInfo.databases` — map keyed by `Space/Database` name. Each entry value is one of: - `'no-access'` — the user has no access. - `'entity-level'` — no space/database-level grant, but the user has access to at least one entity via an entity-level access template. - `{level, templateId, isDefault, url}` — standard template-based access. `level` is the template name with the `app.access/` / `type.access/` prefix stripped. `isDefault: false` indicates a custom template. - `'derived-per-field'` — applies only to `fibery/file` and `comments/comment`; access is granted via per-field grants on the owning database, not at the type level. - `levelInfo.space` and `levelInfo.database` — keyed by `level` (the same string as above); each value carries the template's full title, description, and capability set so the caller can explain what a level grants.

display_schema_capabilities

Fetches a Fibery file attachment by its `secret` and returns a signed download URL valid for ~60 minutes, along with file metadata. For small images and text-ish files, the file contents are also delivered inline so the model can read or analyze them directly without any extra step. The URL expiration timestamp is included in the response. ## What the model receives inline - **Images ≤ 5 MB, Text-ish files ≤ 256 KB**: included in tool's response (you should be able to see them directly) - **Everything else** (PDFs, Office documents, archives, larger files, or unsupported types): only the signed download URL is returned (which is valid for an hour). ## Prerequisites You must already know the file `secret`. Call `get_files_meta` with the entity ID to discover available files and their secrets. ## Example ```json { "secret": "<secret>" } ```

download_file

Creates, updates, or deletes elements (shapes, text, links, sticky notes, sections, freehand pen strokes, ...) on a Fibery Whiteboard. Also returns a `url` for the whiteboard view. **Call `get_fibery_skill({skill: "whiteboard"})` first** — it covers every element type's full property set, the coordinate system, placeholder-ID resolution across calls, and styling/placement conventions. Skipping it leads to invalid or overlapping elements. Element `ID`s may be placeholders you invent (e.g. `"node1"`) — they resolve to real numeric IDs automatically, and the same placeholder always resolves to the same real ID for the rest of the conversation. The returned `idMap` gives you the real ID for each placeholder used in this call; prefer reusing those real IDs directly in later calls over reusing the placeholder string.

execute_whiteboard_commands

Fetches entity or view data from a Fibery URL and renders it as markdown. Accepts URLs in these formats: - Entity: `https://{account}.fibery.io/{Space}/{Type}/{Entity-Title}-{id}` - View: `https://{account}.fibery.io/{Space}/{View-Title}-{id}` Returns formatted markdown with entity fields, document content, or view data including a table of items. ## Examples ``` { "url": "https://myteam.fibery.io/Project_Management/Feature/My-Feature-42" } ``` ``` { "url": "https://myteam.fibery.io/Project_Management/Backlog-7", "limit": 50 } ```

fetch_by_url

Fetches actual entity data from a Fibery View by executing the view's query. This is different from `query_views` which returns view configuration. `fetch_view_data` executes the view's query against the database and returns the entities that the view would display, respecting the view's filters, field selection, and sort order. Prerequisites: call `query_views` first to find the view's publicId. ## Examples ``` { "publicId": "42", "limit": 50 } ```

fetch_view_data

Lists the workspace's connected external app accounts (Slack, email, etc.). Automation actions coming from a non-fibery app (marked `[<app>, requires appAccountId]` in `display_automations_schema`) need one of these account ids as `appAccountId`. Only call this when using an external app action in `create_automation` or `update_automation`.

get_app_accounts

Fetches a single automation rule or button by id, including its triggers, filters and actions with their action ids (needed for `update_automation`). Prefer `get_automations` when the id is unknown. Call `get_fibery_skill({skill: "automations"})` to interpret the returned trigger/filter/action structures. ## Example ``` { automationType: "button", database: "SoftDev/Task", id: "123" } ```

get_automation

Lists all automation rules or buttons of a database, including each automation's id, triggers, filters and actions with their action ids (needed for `update_automation`). Call `get_fibery_skill({skill: "automations"})` to interpret the returned trigger/filter/action structures. ## Example ``` { automationType: "rule", database: "SoftDev/Task" } ```

get_automations

Get a list of available connectors (built-in integrations) in Fibery. Fibery Connectors are built-in integrations that allow users to directly import or continuously sync data from external sources (like Trello, Notion, CSV files and others) into their Fibery workspace. Each connector has a name, id and abilities to import and/or continuously synchronize data. In case the user asks to import data from a source not yet supported, go for CSV option as default — offer to extract data from there and import in Fibery using CSV.

get_connectors_list

List the workspace's custom apps the user can see. Custom apps are small React apps embedded in Fibery views. Use the `id` to work on an app's source code with the custom-app development flow — call `get_fibery_skill({skill: "custom-apps-dev"})` for the full guide.

get_custom_apps_list

Displays Fibery databases schema with fields and related databases in YAML format. The structure is the following: ```yaml {space}/{database}: # Database description fields: {fieldName}: {fieldType} # metadata comments (collection, UI title, read-only, default value, etc.) values: # Only for enum types - id: {enumId} name: {enumName} color: {enumColor} icon: {enumIcon} ``` Metadata comments include: - collection: Field is a collection of references - UI title: Field is used as the display title - read-only: Field value cannot be modified - default: Default value for the field - dependency/dependency start: Field is part of dependency relationships - formula: Field is calculated via formula. Formula is always read-only - values: Available enum values (for enum fields) Use it to explore fields and relations of a database. Prerequisites: call `schema` first to discover available database names.

schema_detailed

Generates Fibery web links for entities based on their public IDs. Public IDs are human-friendly auto-incrementing identifiers (e.g., "42"), different from fibery/id UUIDs. You can get public IDs using `query` tool by selecting the "fibery/public-id" field. ## Examples ``` { "database": "Project Management/Feature", "entityPublicIds": ["42", "43"] } ```

get_entity_links