What a business tool's terms say about customer data
get_tool_termsFor business tools companies keep records in (chat, email, tickets, docs, CRM, call recordings, code hosts): who owns the customer's data, whether the vendor trains AI on it (generative and other models, by plan), whether it keeps aggregated use, what can be exported on which plan and by whom, how much history the plan keeps, and how long data stays after cancellation. Each answer is quoted word for word from the vendor's own terms, AI page, data processing addendum or help article, with the date read. "The terms don't say" means every contract was read and none answers; "Not read yet" means a document is still unread. Answers marked inferred are a reading of the text, not its words. Without a tool id it returns a short index (each tool's headline answers and its Dataconto page); name a tool for the quoted facts. Not legal advice.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_tool_terms"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| plan | No | A plan name as the vendor spells it, e.g. "Free", "Enterprise". | |
| tool | No | Tool id, e.g. "slack", "microsoft-365", "google-workspace", "salesforce", "notion". Omit for a short index of every tool's headline answers. | |
| facts | No | false = headline answers only, no quoted facts. Default true when a tool is named, false otherwise. | |
| field | No | One question: ownership, ai_training, aggregate_use, export, retention or after_cancel. | |
| limit | No | Tools to return, default 20. | |
| answer | No | Keep tools whose headline answer has this token, e.g. opt_out with field=ai_training. | |
| record_type | No | Kind of record: slack-and-teams, email, support-tickets, jira-and-linear, crm, call-recordings, documents-and-sops. |