add_connection
ChatGPTCreate a single-use browser link, valid for ten minutes, where the user can approve another mdbase collection and its permissions. Use it when the user asks to connect, add or approve another collection (for example "connect my reading list too"), or when the collection they mean is not in list_connections. Give the user the link: nothing is approved until they open it and approve in the browser, so call list_connections afterwards and never claim approval happened before it shows the collection.
create_record
ChatGPTCreate one new record in an approved collection. Call read_type first and pass type and frontmatter that satisfy it; omit path to let the collection choose one, and any path you give is collection-relative, never a local file system path. Afterwards tell the user the saved path and fields from the result's outcome.
create_type
ChatGPTCreate a new type definition in an approved collection. A type definition controls validation for every record of that type, so show the user the proposed definition and get their approval before calling. Afterwards tell the user the saved path.
delete_record
ChatGPTPermanently delete one record by its collection-relative path. Before deleting, and always before deleting more than one record, tell the user which records and how many will be deleted and get their explicit confirmation in the conversation; a request such as "delete every task" is not that confirmation. Pass if_revision and check_backlinks true, and tell the user about any records that link to it before going further.
describe_collection
ChatGPTReturn one approved collection's metadata: the operations this connection allows, its types, contracts and current change cursor. Call it once per conversation for each collection before relying on type or field names. It does not change anything.
list_changes
ChatGPTList record changes in one collection after a change cursor; use it to answer what changed. Without after, it returns no events and the current cursor to continue from. typed_events adds record revisions, changed fields and body-change hints when the collection supplies them; unknown events keep their raw payload. If reset is true, the cursor is no longer valid and changes may have been missed: re-read what you rely on with query_records, then continue from the returned cursor.
list_connections
ChatGPTList the mdbase collections the user has approved for this connector and the operations each one allows. Call it first: every other tool needs a connection_id it returns. If the collection the user means is not listed, use add_connection.
query_records
ChatGPTFind records in one approved collection by type and field values, using the mdbase query format for where, order_by and select. Each result has a collection-relative path for read_record and the write tools. Pass the user's IANA timezone when filtering on today() or now(); for large results use pagination "cursor"; output "metadata" returns only path, types, revision and selected values where the collection supports it. It does not change anything.
read_record
ChatGPTRead one record's frontmatter, body and current revision by its collection-relative path, such as tasks/renew-passport.md; never pass a local file system path. Use it to show a record and to get the revision to pass as if_revision before changing or deleting it. It does not change anything.
read_type
ChatGPTRead one type definition, by type name or collection-relative path, with its fields, allowed values and current revision. Call it before filtering on a type's fields or writing a record of that type, and to get the revision update_type needs. It does not change anything.
reconnect_collection
ChatGPTCreate a single-use browser link, valid for ten minutes, that opens the approval screen on one connected collection so the user can renew or broaden its approval. Use it when a tool fails because the collection's approval has lapsed or does not allow the operation. Nothing changes until the user approves in the browser; call list_connections afterwards.
release_query_cursor
ChatGPTRelease an unfinished query_records cursor when you stop paging before the last page. It frees the cursor now instead of waiting for it to expire and does not change any records.
rename_record
ChatGPTRename or move one record to a new collection-relative path, never a local file system path; with update_refs true it also rewrites links to it in other records. It fails if the new path is already taken, but other records may change, so confirm with the user before renaming. Afterwards tell the user the new path and any records whose links changed.
update_record
ChatGPTChange one existing record, overwriting what you supply: patch replaces the given frontmatter fields, body replaces the body and document replaces the whole file. Read the record first and pass its revision as if_revision so a concurrent edit is not overwritten; path is collection-relative, never a local file system path, and ask the user before changing more than a few records. Afterwards tell the user the saved path and the fields that changed.
update_type
ChatGPTReplace an existing type definition. A type definition controls validation for every record of that type, so show the user the proposed definition and what changes from the current one, and get their explicit approval before calling; a request to change a type is not approval of a specific definition. Pass the revision from read_type as if_revision.
validate_collection
ChatGPTCheck the records in one collection against their type definitions and return the validation issues. Optional input is passed to the collection's validation operation. It reports problems only and does not change anything.
add_connection
Claudecreate_record
Claudecreate_type
Claudedelete_record
Claudedescribe_collection
Claudelist_changes
Claudelist_connections
Claudequery_records
Clauderead_record
Clauderead_type
Claudereconnect_collection
Clauderelease_query_cursor
Clauderename_record
Claudeupdate_record
Claudeupdate_type
Claudevalidate_collection
Claude