ChatData Sync

Adds a new field to a section in a tracker's layout, up to the per-section field limit. Call describe_schema first to see existing sections and fields. Set type to one of: text, number, boolean, date, time, choice, or reference. For a choice field, pass the allowed values in 'choices'. For a reference field (a link/relationship to another section), pass the target section id in 'references_section'. Only the account owner can change a tracker's layout. This does not delete any existing data.

add_field

Adds a new section (table) to a tracker's layout, up to the account's plan limit. Provide a short, human-friendly name (for example "Clients" or "Payments"); it is turned into a section id automatically. The new section starts with a single starter "name" text field; use add_field to add more fields. Only the account owner can change a tracker's layout. This does not delete any existing data.

add_section

Creates one record in the selected tracker. Call get_sync_context first, then pass record_json as a JSON object string using only the exact field names it returns. Map field types as follows: text -> string, number -> number, boolean -> true/false, date -> YYYY-MM-DD, time -> HH:MM, choice -> one of the allowed strings. Omit optional fields rather than passing null. For retry-safe HTTP calls, send an Idempotency-Key header; the same key and payload replay the original response.

create_record

Creates a new tracker only when the connection has explicit account-wide write access. Tracker-scoped connections cannot use this tool. Provide a short, human-friendly name (for example: "Garden Log" or "Client Invoices"). The account's tracker limit is enforced.

create_tracker

Deletes one record from the API-key scoped tracker by ID. Pass expectedRevision to prevent deleting a record changed by another client. Send an Idempotency-Key header to replay a retried delete, including after the first delete has completed.

delete_record

Returns the full editable layout of a tracker: every section (table), its fields with their type (text | number | boolean | date | time | choice | reference), whether each field is required, the allowed values for choice fields, and which section a reference field links to. Also returns the plan limits and how many sections and fields are currently used. Call this before add_section or add_field so you know the current layout and remaining capacity.

describe_schema

Creates a single-use private download URL for one attachment after rechecking tracker, record, and attachment access. Use only when the user wants to open or analyze a specific listed file. The URL expires after five minutes if unused and must not be stored as a permanent reference.

get_attachment_link

Reads one record from the API-key scoped tracker by ID.

get_record

Returns the tracker name, default table, available tables, and field definitions scoped to the supplied API key. Call this once before any read or write operation. The returned tables[].fields array defines every valid field name, its type (text | number | boolean | date | time | choice), whether it is required, and—for choice fields—the allowed values. Use these definitions as the authoritative schema for all subsequent create_record and update_record calls.

get_sync_context

Lists private document, spreadsheet, text, and image attachments for one record. Use this before get_attachment_link when the user asks what files are attached. Returns metadata only and never exposes storage paths or provider file IDs.

list_attachments