ActivityInfo.org

List the ActivityInfo databases the user can access. Call this first to discover the databaseId that every other tool requires. Each entry has an `mcpServerEnabled` flag: when it is false, every other tool will refuse the database and the owner must enable the MCP server in the database's Security section first.

listDatabases

List all fields (columns) of a form, including subform references. Returns each field's code, name, type and other properties.

listFields

List the forms and reports in an ActivityInfo database. Each entry has a `type` of FORM or REPORT; forms carry their name and folder path, reports carry their id, name, and an absolute web URL the user can open. Use this to discover what's in the database before drilling in with listFields, getReport, addPivotsToReport, etc.

listResources

List the translation dictionaries in a database: one for the database tree (database/folder/form/role labels) and one per form (field labels, descriptions, units, enum options). Each entry has an opaque `id` to pass to getTranslations / updateTranslations, plus a `description` naming what the dictionary contains.

listTranslationDictionaries

Run a pivot-table analysis to answer an analytical question about the data, and return the aggregated result. Provide one or more measures (what to aggregate, e.g. SUM of a quantity field, or COUNT of records) and optional row/column dimensions (how to group, e.g. by a category field or by month). Each measure and dimension names its own form; a dimension may use a related form and the relationship is resolved automatically. Returns CSV by default, or a flat list of row objects with format=JSON.

pivot

Update existing fields of a form, matched by code: changes name, description, required, options, formula or reference target in place, preserving the field and its data. The field type cannot be changed (delete and re-add the field for that).

updateFields

Update existing records of a form. Each record object must include the `_id` returned by getRecords; other keys are field codes whose values should change. Fields not present in the record object keep their existing values; pass JSON null to clear a field. Read-only field types (calculated, serial, attachment, subform, section header, reverse reference) are silently ignored.

updateRecords

Save translations for a dictionary. The server validates each entry against the current schema: entries with an unknown `key` or a drifted `original` are silently dropped, so always send back the rows you just received from getTranslations with only the `translation` filled in. Form labels are mirrored between the database-tree dictionary and the form's own dictionary automatically.

updateTranslations