apply_template
ChatGPTSet up a ready-made collection from a built-in template: 'kakeibo' (家計簿 expense tracking), 'tango' (単語帳 vocabulary notebook), 'kenko' (健康ログ health log). Prefer this over create_collection when the user's need matches. Idempotent. The result includes a usage hint — follow it.
create_collection
ChatGPTCreate a new typed collection (like a table) for a kind of thing the user wants to track. Infer the field list from the user's intent: amounts/prices → type 'number'; calendar dates → 'date'; categories with a small fixed set of values → 'select' with options; free text → 'text'. Keep fields minimal (2-5). Use snake_case English keys and labels in the user's language. Idempotent: if a collection with the same slug already exists, the existing one is returned unchanged.
delete_record
ChatGPTDelete one record. It stays in the history log and can be restored with undo_change. Use when the user says 'delete that'. Find recordId with query_records.
delete_view
ChatGPTRemove a screen (by id or title). Kept in history and can be undone with undo_change.
get_access_status
ChatGPTShow whether the hosted buddybase connection is available to this user (buddybase Pro). Use it when a tool returns subscription_required. Works without the plan.
get_thing
ChatGPTThings are what records are about (shops, people, words…) across collections. Fields marked identity (e.g. 家計簿's 'shop', 単語帳's 'word') with the same value already count as the same thing. One thing (by name) and all its records across collections.
history
ChatGPTShow the history log: who changed what, when, and why. Narrow it to one record (recordId) or one collection. Each entry has a seq you can pass to undo_change. Newest last.
link
ChatGPTConnect two records or things with a direction and a kebab-case label (e.g. from a dinner record to the next night's sleep record, label 'next-day'; from a word to a book, label 'source'). Links are not 'same': they say two different things are related. Kept in history and can be undone with undo_change.
list_collections
ChatGPTList the user's collections with record counts. Call this before creating a collection or when unsure which slug to save into.
list_links
ChatGPTWhat is linked to a record (from = record id) or a thing (from = name).
list_things
ChatGPTThings are what records are about (shops, people, words…) across collections. Fields marked identity (e.g. 家計簿's 'shop', 単語帳's 'word') with the same value already count as the same thing. List things (optionally one kind) with how often they appear.
list_views
ChatGPTThe user's screens (views), pinned first.
merge_things
ChatGPTThe user confirmed a and b are the same thing; merge them. Kept in history and can be undone with undo_change.
query_records
ChatGPTQuery records in a collection: filter, sort, limit, or aggregate (sum/count/avg, optionally grouped by a field key or by 'day'/'week'/'month'). Use aggregate for questions like 'how much did I spend this month?'. filter on 'recordedAt' (epoch ms) with gt/lt to restrict a time range.
save_record
ChatGPTSave one record into a collection. 'values' keys must match the collection's field keys (call list_collections first if unsure). Convert what the user said into typed values (e.g. 'ランチ1200円' → {amount: 1200, category: '食費', note: 'ランチ'}). Anything that does not fit a field goes into 'note'. recordedAt is when the thing happened (ISO string or epoch ms); omit for 'now'. The result includes a summary — tell the user one stat from it (e.g. this month's total).
save_view
ChatGPTCreate or replace a screen the user will see in the buddybase iPhone app, on the web, and here in chat. Use it when the user asks for a dashboard, a widget or a screen for their records. Omit viewId to create; pass viewId to replace the whole design. Check list_collections first for slugs and field keys. If the design has problems, the result lists them with their paths — fix and call again. Kept in history; undo with undo_change. A view is a JSON design: { title, icon?, accent?, body: [parts] }. Data is not copied into it: each data part has a source { collection, period?, filters?, aggregate?, sort?, limit? } and the latest values are filled in every time it is shown. period: today, yesterday, this_week, last_week, this_month, last_month, last_7_days, last_30_days, this_year, all (JST). aggregate: { op: sum|count|avg, field?, groupBy? (field key or day|week|month) }. Parts: stack {direction?, children} · grid {columns 1-4, children} · section {title, children} · text {text, style: title|body|caption} · stat {label, source with aggregate, compare?: 'previous_period'} · chart {style: bar|line|donut, label?, source with aggregate.groupBy} · list / table {label?, source without aggregate, fields?} · progress {label, source with aggregate, goal} · thing {name, kind?} · links {from, kind?, label?} · timeline {label?, collection?, limit?} · quick_add {label?, collection, fields, defaults?} (a form that saves a record) · custom {html, height?, data?: {name: source}} — only when no part fits: self-contained HTML+JS, no network; it receives window.buddybase.data and may call window.buddybase.saveRecord(collection, values), which the user confirms. accent: ink, red, orange, yellow, green, teal, blue, purple, pink. Max 60 parts, depth 6, 20 sources. Prefer parts over custom: parts look native on iPhone and can be home-screen widgets; custom cannot.
separate_things
ChatGPTThe user says a and b are different things; split them. Kept in history and can be undone with undo_change.
show_view
ChatGPTShow a screen with its latest data (by id or title), here in chat. Also returns the design, so you can change it with save_view.
suggest_links
ChatGPTRecords in other collections on the same day as a record that may be related. Never writes — ASK the user how they are related before calling link.
suggest_same
ChatGPTThings are what records are about (shops, people, words…) across collections. Fields marked identity (e.g. 家計簿's 'shop', 単語帳's 'word') with the same value already count as the same thing. Names that may be the same thing (e.g. 'なか卯' and 'なか卯 四条店'). Never writes — ASK the user before calling merge_things.
undo_change
ChatGPTUndo a change (records, collection changes, same/separate decisions, links). Pass eventSeq from the history tool, or omit it to undo the latest change (call again to go further back). Use when the user says 'undo'.
unlink
ChatGPTRemove a link by linkId (find it with list_links). Kept in history and can be undone with undo_change.
update_collection
ChatGPTChange an existing collection: rename it, add fields, or change a field's label, unit, kind or identity. Use identity + kind to make records about the same thing group together (e.g. mark 家計簿's shop field as kind 'place', identity true). Field keys and types cannot be changed and fields cannot be removed, so existing records keep their meaning. Kept in history; undo with undo_change.
update_record
ChatGPTFix some values of a record (only the keys you pass; null clears a value). Kept in the history log and can be undone with undo_change. Use when the user says 'that was wrong' or 'change it to …'. Find recordId with query_records.