Support: diagnose the workspace and MCP itself
atisbo_supportDiagnose Atisbo, including "I connected a source and nothing appeared", "I sent text and no opportunity formed", or "my data is missing". Checks integrations, ingestion, clustering, gates, key scope and migrations, then returns a playbook. share_report files only diagnostics + your text. Use atisbo_lookup/atisbo_analyze for backlog.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"problem": "<problem>"
},
"name": "atisbo_support"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| area | No | Narrows the checks. Omit when unsure. | |
| problem | Yes | What went wrong, in your words. No customer feedback, docs or credentials — the string IS filed in reports. | |
| share_report | No | File a verdict-only report when the fault is not caller-side; false = diagnose. | |
| observed_error | No | The failing error VERBATIM — usually the only evidence. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| meta | Yes |