Skip to content

Tools of the assistant

A connected assistant only sees the tools the user is authorized for. This reference lists all 55 tools, their meaning and the prerequisite, checked against Pantarey's tool catalog. Tool names appear in answers, in approvals and in the log; they are not needed in the conversation.

Orientation

Tool Meaning Prerequisite
get_company_info Description, terms, rules and contact of the company Role "connect"
get_usage Own limits and usage of the current hour Role "connect"
count_workdays Working days between two dates with the account's work calendar, also for part time and half days; per year over the turn of the year Workspace
get_work_calendar Public holidays, half days and company days off of the account in a period Workspace

Read data

Tool Meaning Prerequisite
list_data_schemas All permitted data schemas Read data schemas
get_data_schema Fields of a data schema with descriptions: field type, required fields, value lists, references, sub-fields of objects and lists, rules Read data schemas
get_permissions Permissions of a data schema: who may do what, conditions, denies, descriptions Read permissions (Data Designer, administrators)
list_users Users of the account with e-mail and groups, optionally filtered Read user directory (Data Designer, administrators)
list_groups User groups, optionally with their members Read group directory (Data Designer, administrators)
explain_access Why a user may or may not do something – for a schema or one record, with the deciding entry Read permissions (Data Designer, administrators)
get_permissions_guide Explains permissions, conditions and denies to the assistant, and what to ask before a change Read permissions (Data Designer, administrators)
search_data_objects Full-text search within a data schema Read data objects
list_records Browse the folder tree of a data schema Read data objects
filter_records Filter records by an indexed field value Read data objects
get_data_object Read one record completely, including references Read data objects
get_file Download link for a file of a record (valid 15 minutes) Read files

Analyze

Tool Meaning Prerequisite
list_tables Analytics tables that may be queried Analytics
query_records Run a SQL query (read only) Analytics, ad-hoc queries
get_query_result Fetch the result of a query Analytics, ad-hoc queries

Write data

Tool Meaning Prerequisite
create_record Create a record, with a dry run without saving Write data objects and role "write records directly"
create_records Create up to 100 records of one data schema at once – all or none, with a dry run without saving Write data objects and role "write records directly"
update_record Change fields of a record Write data objects and role "write records directly"

Building (developer mode)

Tool Meaning Prerequisite
create_data_schema Create a new data schema with fields, as in the Data Designer; with dry run, existing data schemas are never overwritten Create data schemas and role "build (developer mode)" and developer mode active; AI approval by default
add_data_schema_fields Add fields to an existing data schema, also inside objects and lists as above
update_data_schema_field Change the title, description, required, preview, hidden flag or value list of a field as above
delete_data_schema_field Delete a field permanently; dry run and approval list all consequences as above
update_data_schema Change the display name and description of a data schema as above
reorder_data_schema_fields Change the order of the fields as above
update_data_schema_rules Add, change, switch off or remove rules, tried on examples first as above
add_data_schema_permission Add a permission (allow or deny, with condition and description); dry run and approval show what changes for each user Edit permissions and role "build (developer mode)" and developer mode active; AI approval by default
update_data_schema_permission Change a permission: who, what and for which records as above
delete_data_schema_permission Delete a permission as above
test_jsonata Try a JSONata expression on example data without saving Role "build (developer mode)"; no approval
check_record Check whether a record would be accepted when saved, without saving Read data schemas and role "build (developer mode)"; no approval
change_dashboard Change settings and titles of widgets in an AI copy of the dashboard, also add or remove list items; with dry run, taken over in the AI panel Edit dashboards in the Dashboard Designer and role "build (developer mode)" and developer mode active; no approval by default
create_process Create a new, empty process (start and end), like New in the Process Designer; not deployed Edit processes in the Process Designer and role "build (developer mode)" and developer mode active; no approval by default
change_process Change a process in an AI copy: steps, gateways, forms, databases, starts, "throw signal"; with dry run, taken over in the AI mode of the Process Designer as create_process

More under Building with the assistant.

Dashboards

Tool Meaning Prerequisite
list_dashboards Dashboards with name and whether they are deployed Edit dashboards in the Dashboard Designer
get_dashboard One dashboard with its widgets; one widget in full with every setting explained, or only single settings in full as above
get_dashboard_guide How the widgets work, with examples and rules for SQL in widgets as above

Changing: change_dashboard under Building (developer mode), sequence under Changing dashboards with the assistant.

Processes

Tool Meaning Prerequisite
list_processes Available processes Read processes
get_process_start_schema Start form of a process Read processes
start_process Start a process with a filled-in start form Start processes and role "start processes and complete tasks"
list_process_instances Cases of a process Process Explorer
get_process_instance Status of a case Process Explorer
my_start_events Own startable actions (like the "Start processes" card) Workspace
my_running_instances Own running cases Workspace
recent_process_activity Recent activity Workspace
process_stats Process statistics Workspace
get_process A process step by step with its settings, for building; one element in full Read processes and role "build (developer mode)"
get_process_guide How Pantarey runs processes, with examples, for the assistant when building Role "build (developer mode)"
list_service_tasks Which service tasks exist and which input they need Role "build (developer mode)"

Building: create_process and change_process under Building (developer mode), sequence under Building processes with the assistant.

Tasks

Tool Meaning Prerequisite
my_open_tasks Own open tasks Workspace
get_task Form and data of a task Workspace
complete_task Complete a task Work on tasks and role "start processes and complete tasks"

How answers are structured

Besides the data, every answer contains a note on what it means for the user, suggestions for sensible next steps and links into the Pantarey app. Truncated lists are marked as such. Writing tools validate the input before saving and refuse duplicate executions of the same request.

Tips

  • Use the dry run: Before creating a record or a data schema, the assistant can have the input checked without saving. A dry run never needs an AI approval.
  • Create many records: On "Create these 300 contacts", the assistant creates the records in batches of up to 100. If one record of a batch is invalid, none of that batch is saved; the dry run lists all errors beforehand with the number of the record. Every record counts separately against the hourly limit.
  • Follow the links: Where the chat cannot continue – deleting, uploading files – the link leads straight to the right place in Pantarey.

Next step

Back to the Overview or on to Building with the assistant, where the build tools are explained in context.