volanea_report_missing_tool
Read-only
Report that this server lacks a tool you needed, so the gap gets closed instead of silently worked around. Call it at the moment you fall back to a raw REST call, tell the user to do something by hand in the dashboard, or abandon an approach because no tool covered it — those are the three signals that matter, and none of them is visible to anyone unless you say so. IMPORTANT: this records feedback and changes NOTHING about the project; it does not create the missing capability, retry your last call, or unblock you. After calling it, carry on with the REST API — volanea_get_api_reference has the endpoint you need. Costs one call and is always safe: it is write-free and reads no project data.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | What you were building and what you did instead. The workaround is the useful half: it shows which REST endpoint the tool should have wrapped, and how awkward the detour was. | |
| capability | Yes | The missing capability in one line, phrased as the operation you wanted — e.g. "check whether an address is suppressed" or "list scheduled sends". Not the symptom, and not the workaround you settled on. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | Machine-readable failure code to branch on. Present only when success is false. | |
| data | No | Present when success is true. | |
| error | No | Human-readable failure reason. Present only when success is false. | |
| success | Yes | False when the call failed; read `error` and `code` in that case. |